Update package-lock.json files for 0.16.0

Author: sodic

examples/hackathon-submissions/package-lock.json

@@ -14,6 +14,6 @@
     "prisma": "5.19.1",
     "typescript": "^5.1.0",
     "vite": "^4.3.9",
-    "wasp-config": "file:../../../../../.local/share/wasp-lang/0.15.0/data/packages/wasp-config"
+    "wasp-config": "file:../../../../../.local/share/wasp-lang/0.16.0-rc2/data/packages/wasp-config"
   }
 }

examples/streaming/package-lock.json

@@ -1,48 +1,7 @@
-// =============================== IMPORTANT =================================
-// This file is mainly used for Wasp IDE support.
-//
-// 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.
-    "moduleResolution": "bundler",
-    // JSX support
-    "jsx": "preserve",
-    "strict": true,
-    // Allow default imports.
-    "esModuleInterop": true,
-    "lib": [
-      "dom",
-      "dom.iterable",
-      "esnext"
-    ],
-    "skipLibCheck": true,
-    "allowJs": true,
-    "typeRoots": [
-      // This is needed to properly support Vitest testing with jest-dom matchers.
-      // Types for jest-dom are not recognized automatically and Typescript complains
-      // about missing types e.g. when using `toBeInTheDocument` and other matchers.
-      "node_modules/@testing-library",
-      // Specifying type roots overrides the default behavior of looking at the
-      // node_modules/@types folder so we had to list it explicitly.
-      // Source 1: https://www.typescriptlang.org/tsconfig#typeRoots 
-      // Source 2: https://github.com/testing-library/jest-dom/issues/546#issuecomment-1889884843
-      "node_modules/@types"
-    ],
-    "outDir": ".wasp/out/user"
-  },
-  "include": [
-    "src"
+  "files": [],
+  "references": [
+    { "path": "./tsconfig.src.json" },
+    { "path": "./tsconfig.wasp.json" }
   ]
 }

examples/thoughts/package-lock.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,11 +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"]
+  "include": [
+    "src"
+  ]
 }