@_linked/cli 1.6.3 → 1.6.4
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,20 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 1.6.4
|
|
4
|
+
|
|
5
|
+
### Patch Changes
|
|
6
|
+
|
|
7
|
+
- [#48](https://github.com/linked-cm/cli/pull/48) [`dce9cb5`](https://github.com/linked-cm/cli/commit/dce9cb5e669b40f131494bbf5ed5c6990bb02cb3) Thanks [@flyon](https://github.com/flyon)! - Template `tsconfig.json` switched from `moduleResolution: "node"` to `moduleResolution: "bundler"`. The classic Node resolver doesn't honor the `exports` field in package.json, and `@_linked/react` (and friends) declare types only inside `exports[".".types]`, not as a top-level `types` field. The result was a fresh scaffold compiling cleanly with yarn install but exploding under webpack/ts-loader:
|
|
8
|
+
|
|
9
|
+
```
|
|
10
|
+
TS2307: Cannot find module '@_linked/react' or its corresponding type declarations.
|
|
11
|
+
There are types at '.../node_modules/@_linked/react/lib/esm/index.d.ts', but
|
|
12
|
+
this result could not be resolved under your current 'moduleResolution' setting.
|
|
13
|
+
Consider updating to 'node16', 'nodenext', or 'bundler'.
|
|
14
|
+
```
|
|
15
|
+
|
|
16
|
+
`bundler` is the right choice for a webpack-bundled app — it honors `exports`, doesn't require `.js` extensions on relative imports, and doesn't enforce full ESM strictness.
|
|
17
|
+
|
|
3
18
|
## 1.6.3
|
|
4
19
|
|
|
5
20
|
### Patch Changes
|
package/lib/cjs/package.json
CHANGED
package/lib/esm/package.json
CHANGED