@_linked/cli 1.21.2 → 1.21.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.
Files changed (2) hide show
  1. package/CHANGELOG.md +42 -0
  2. package/package.json +4 -5
package/CHANGELOG.md CHANGED
@@ -1,5 +1,47 @@
1
1
  # Changelog
2
2
 
3
+ ## 1.21.4
4
+
5
+ ### Patch Changes
6
+
7
+ - [#118](https://github.com/linked-fw/cli/pull/118) [`e9050cf`](https://github.com/linked-fw/cli/commit/e9050cf77f63c6b98d2cf657aeb5cfd1ee81c2c4) Thanks [@flyon](https://github.com/flyon)! - Compile the whole `src` folder, and let a bare import resolve under Node10.
8
+
9
+ The build only emitted what an entry transitively reached, so any module
10
+ nothing imported was never built — and never type-checked, so it rotted
11
+ quietly. `include` now covers `src/**/*` with tests excluded explicitly.
12
+
13
+ `typesVersions` maps every specifier through `lib/esm/*`, so a `types` value
14
+ that already carried that prefix had it applied twice and no consumer on
15
+ classic Node10 resolution could `import` the package by its bare name.
16
+
17
+ ## 1.21.3
18
+
19
+ ### Patch Changes
20
+
21
+ - [#116](https://github.com/linked-fw/cli/pull/116) [`0377581`](https://github.com/linked-fw/cli/commit/0377581afa4e97070a70f7cc263f2baf6d5e4a9d) Thanks [@flyon](https://github.com/flyon)! - Drop `optimize-css-assets-webpack-plugin`, so `npm install` and `npm ci` work without `--legacy-peer-deps`.
22
+
23
+ The package declares `webpack ^5`, but this plugin's last release peers on
24
+ `webpack ^4`. npm cannot satisfy both, so a plain install failed outright:
25
+
26
+ ```
27
+ npm error ERESOLVE could not resolve
28
+ npm error While resolving: optimize-css-assets-webpack-plugin@6.0.1
29
+ npm error Found: webpack@5.108.4
30
+ npm error Could not resolve dependency: peer webpack@"^4.0.0"
31
+ ```
32
+
33
+ The workaround was `--legacy-peer-deps`, which silences every peer check in the
34
+ tree, not just this one — and it left `npm ci` broken, so a clean
35
+ lockfile-driven install never worked at all.
36
+
37
+ Nothing imports the plugin: it appears only in `devDependencies`, with no
38
+ reference anywhere in `src/`. It is also deprecated upstream in favour of
39
+ `css-minimizer-webpack-plugin`, which is not needed here either, since the
40
+ webpack config does not minify CSS through it.
41
+
42
+ Removing it is the whole fix. `npm install` and `npm ci` both succeed with no
43
+ flags, 28 fewer packages are installed, and the audit total drops from 20 to 19.
44
+
3
45
  ## 1.21.2
4
46
 
5
47
  ### Patch Changes
package/package.json CHANGED
@@ -1,10 +1,10 @@
1
1
  {
2
2
  "name": "@_linked/cli",
3
- "version": "1.21.2",
3
+ "version": "1.21.4",
4
4
  "packageManager": "npm@11.19.1",
5
5
  "description": "Command line tools for the @_linked/* packages and apps",
6
6
  "main": "lib/esm/index.js",
7
- "types": "./lib/esm/index.d.ts",
7
+ "types": "index.d.ts",
8
8
  "module": "lib/esm/index.js",
9
9
  "exports": {
10
10
  ".": {
@@ -91,8 +91,8 @@
91
91
  "@tailwindcss/postcss": "^4.1.4",
92
92
  "@tailwindcss/vite": "^4.1.4",
93
93
  "@types/node": "^20.12.7",
94
- "@types/react": "^18.0.17",
95
- "@types/react-dom": "^18.0.6",
94
+ "@types/react": "^19.3.0",
95
+ "@types/react-dom": "^19.3.0",
96
96
  "@vitejs/plugin-react": "^4.3.0",
97
97
  "babel-loader": "^9.1.3",
98
98
  "chalk": "^4.1.2",
@@ -154,7 +154,6 @@
154
154
  "babel-jest": "^29.7.0",
155
155
  "husky": "^9.0.11",
156
156
  "jest": "^29.7.0",
157
- "optimize-css-assets-webpack-plugin": "^6.0.1",
158
157
  "pinst": "^3.0.0",
159
158
  "prettier": "^3.2.5",
160
159
  "testcontainers": "^10.13.2"