Migrate waspc/examples apps to 0.16.0 (#2467)

waspc/examples/crud-testing/main.wasp

@@ -1,6 +1,6 @@
 app crudTesting {
   wasp: {
-    version: "^0.15.0"
+    version: "^0.16.0"
   },
   head: [
     "<link rel=\"stylesheet\" href=\"https://unpkg.com/[email protected]/mvp.css\">"

waspc/examples/crud-testing/tsconfig.json

@@ -1,11 +1,18 @@
 // =============================== IMPORTANT =================================
+// This file is mainly used for Wasp IDE support.
 //
-// This file is only used for Wasp IDE support. You can change it to configure
-// your IDE checks, but none of these options will affect the TypeScript
-// compiler. Proper TS compiler configuration in Wasp is coming soon :)
+// Wasp will compile your code with slightly different (less strict) compilerOptions.
+// You can increase the configuration's strictness (e.g., by adding
+// "noUncheckedIndexedAccess": true), but you shouldn't reduce it (e.g., by
+// adding "strict": false). Just keep in mind that this will only affect your
+// IDE support, not the actual compilation.
+//
+// Full TypeScript configurability is coming very soon :)
 {
   "compilerOptions": {
     "module": "esnext",
+    // Needed because this is used as a project reference.
+    "composite": true,
     "target": "esnext",
     // We're bundling all code in the end so this is the most appropriate option,
     // it's also important for autocomplete to work properly.
@@ -20,6 +27,7 @@
       "dom.iterable",
       "esnext"
     ],
+    "skipLibCheck": true,
     "allowJs": true,
     "typeRoots": [
       // This is needed to properly support Vitest testing with jest-dom matchers.
@@ -32,10 +40,9 @@
       // Source 2: https://github.com/testing-library/jest-dom/issues/546#issuecomment-1889884843
       "node_modules/@types"
     ],
-    // Since this TS config is used only for IDE support and not for
-    // compilation, the following directory doesn't exist. We need to specify
-    // it to prevent this error:
-    // https://stackoverflow.com/questions/42609768/typescript-error-cannot-write-file-because-it-would-overwrite-input-file
-    "outDir": ".wasp/phantom"
-  }
+    "outDir": ".wasp/out/user"
+  },
+  "include": [
+    "src"
+  ]
 }

waspc/examples/pg-vector-example/main.wasp

@@ -1,6 +1,6 @@
 app pgVectorExample {
   wasp: {
-    version: "^0.15.0"
+    version: "^0.16.0"
   },
   title: "PG Vector Example",
   client: {

waspc/examples/pg-vector-example/tsconfig.json

@@ -1,11 +1,18 @@
 // =============================== IMPORTANT =================================
+// This file is mainly used for Wasp IDE support.
 //
-// This file is only used for Wasp IDE support. You can change it to configure
-// your IDE checks, but none of these options will affect the TypeScript
-// compiler. Proper TS compiler configuration in Wasp is coming soon :)
+// Wasp will compile your code with slightly different (less strict) compilerOptions.
+// You can increase the configuration's strictness (e.g., by adding
+// "noUncheckedIndexedAccess": true), but you shouldn't reduce it (e.g., by
+// adding "strict": false). Just keep in mind that this will only affect your
+// IDE support, not the actual compilation.
+//
+// Full TypeScript configurability is coming very soon :)
 {
   "compilerOptions": {
     "module": "esnext",
+    // Needed because this is used as a project reference.
+    "composite": true,
     "target": "esnext",
     // We're bundling all code in the end so this is the most appropriate option,
     // it's also important for autocomplete to work properly.
@@ -20,6 +27,7 @@
       "dom.iterable",
       "esnext"
     ],
+    "skipLibCheck": true,
     "allowJs": true,
     "typeRoots": [
       // This is needed to properly support Vitest testing with jest-dom matchers.
@@ -32,10 +40,9 @@
       // Source 2: https://github.com/testing-library/jest-dom/issues/546#issuecomment-1889884843
       "node_modules/@types"
     ],
-    // Since this TS config is used only for IDE support and not for
-    // compilation, the following directory doesn't exist. We need to specify
-    // it to prevent this error:
-    // https://stackoverflow.com/questions/42609768/typescript-error-cannot-write-file-because-it-would-overwrite-input-file
-    "outDir": ".wasp/phantom"
-  }
+    "outDir": ".wasp/out/user"
+  },
+  "include": [
+    "src"
+  ]
 }

waspc/examples/todo-typescript/main.wasp

@@ -1,6 +1,6 @@
 app TodoTypescript {
   wasp: {
-    version: "^0.15.0"
+    version: "^0.16.0"
   },
   title: "ToDo TypeScript",
 

waspc/examples/todo-typescript/tsconfig.json

@@ -1,11 +1,18 @@
 // =============================== IMPORTANT =================================
+// This file is mainly used for Wasp IDE support.
 //
-// This file is only used for Wasp IDE support. You can change it to configure
-// your IDE checks, but none of these options will affect the TypeScript
-// compiler. Proper TS compiler configuration in Wasp is coming soon :)
+// Wasp will compile your code with slightly different (less strict) compilerOptions.
+// You can increase the configuration's strictness (e.g., by adding
+// "noUncheckedIndexedAccess": true), but you shouldn't reduce it (e.g., by
+// adding "strict": false). Just keep in mind that this will only affect your
+// IDE support, not the actual compilation.
+//
+// Full TypeScript configurability is coming very soon :)
 {
   "compilerOptions": {
     "module": "esnext",
+    // Needed because this is used as a project reference.
+    "composite": true,
     "target": "esnext",
     // We're bundling all code in the end so this is the most appropriate option,
     // it's also important for autocomplete to work properly.
@@ -20,6 +27,7 @@
       "dom.iterable",
       "esnext"
     ],
+    "skipLibCheck": true,
     "allowJs": true,
     "typeRoots": [
       // This is needed to properly support Vitest testing with jest-dom matchers.
@@ -32,10 +40,9 @@
       // Source 2: https://github.com/testing-library/jest-dom/issues/546#issuecomment-1889884843
       "node_modules/@types"
     ],
-    // Since this TS config is used only for IDE support and not for
-    // compilation, the following directory doesn't exist. We need to specify
-    // it to prevent this error:
-    // https://stackoverflow.com/questions/42609768/typescript-error-cannot-write-file-because-it-would-overwrite-input-file
-    "outDir": ".wasp/phantom"
-  }
+    "outDir": ".wasp/out/user"
+  },
+  "include": [
+    "src"
+  ]
 }