@object-ui/create-plugin 16.1.0 → 17.1.0
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 +57 -0
- package/package.json +4 -3
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,62 @@
|
|
|
1
1
|
# @object-ui/create-plugin
|
|
2
2
|
|
|
3
|
+
## 17.1.0
|
|
4
|
+
|
|
5
|
+
## 17.0.0
|
|
6
|
+
|
|
7
|
+
### Patch Changes
|
|
8
|
+
|
|
9
|
+
- 5b9cf96: fix(plugin-map): drop the `maplibre-gl@6` default import, and put type-check behind a CI gate that cannot be silently skipped (#2911)
|
|
10
|
+
|
|
11
|
+
`maplibre-gl@6.0.0` removed its default export (arrived via #2848, dependabot),
|
|
12
|
+
so `ObjectMap.tsx`'s `import maplibregl from 'maplibre-gl'` has been a TS1192
|
|
13
|
+
error on `main` for a day. The binding was never used — the map instance comes
|
|
14
|
+
from `react-map-gl/maplibre`, and the stylesheet from the side-effect import on
|
|
15
|
+
the next line — so the import is simply deleted rather than rewritten to
|
|
16
|
+
`import * as`.
|
|
17
|
+
|
|
18
|
+
Removing it is runtime-neutral, which the issue had explicitly left unverified.
|
|
19
|
+
`@vis.gl/react-maplibre` (what `react-map-gl/maplibre` re-exports) does
|
|
20
|
+
`Promise.resolve(mapLib || import('maplibre-gl'))` in `components/map.js`, so it
|
|
21
|
+
loads the library itself when no `mapLib` prop is passed. Verified in a browser
|
|
22
|
+
against the `store-locator-map` catalog schema: `maplibre-gl` is fetched as its
|
|
23
|
+
own lazy chunk, the WebGL canvas comes up 800x600, and all three markers mount —
|
|
24
|
+
byte-identical probe output with and without the static import. That also matches
|
|
25
|
+
what `apps/console/src/main.tsx` already intends, where the plugin is registered
|
|
26
|
+
lazily specifically to keep `maplibre-gl` out of the initial bundle.
|
|
27
|
+
|
|
28
|
+
**The reason it survived a day of green CI is the part worth fixing.** No
|
|
29
|
+
workflow ran `type-check` at all, and `turbo build` only checks types for
|
|
30
|
+
packages whose `build` script happens to invoke `tsc` — the 22 `vite build`
|
|
31
|
+
packages transpile without checking. A sweep of all 45 packages found ten with
|
|
32
|
+
broken types, `plugin-map` merely being the one that had a script to notice it.
|
|
33
|
+
|
|
34
|
+
Adding a `pnpm type-check` job alone would not have been a gate: **turbo silently
|
|
35
|
+
skips any package with no `type-check` script**, so 17 packages read as passing
|
|
36
|
+
because nothing ran. With `plugin-map` fixed, `pnpm type-check` reports 63/63
|
|
37
|
+
green while nine packages are still broken. So:
|
|
38
|
+
|
|
39
|
+
- `plugin-ai` and `plugin-report` gain the `paths` override their type-checked
|
|
40
|
+
peers already carry, which detaches workspace deps from sibling _source_ and
|
|
41
|
+
resolves them through built `.d.ts` — the sole cause of the 104-error TS6059
|
|
42
|
+
`rootDir` floods, and the same trick their own `vite.config.ts` already applies
|
|
43
|
+
to the dts program.
|
|
44
|
+
- Seven packages gain `"type-check": "tsc --noEmit"` (`plugin-ai`,
|
|
45
|
+
`plugin-report`, `plugin-dashboard`, `create-plugin`, `console`, and the two
|
|
46
|
+
console examples). Coverage goes 28 -> 35 of 45.
|
|
47
|
+
- New `scripts/check-type-check-coverage.mjs` makes the invisibility impossible:
|
|
48
|
+
a package with no `type-check` script must be declared, with a reason, and the
|
|
49
|
+
lists only shrink — gaining a script without deleting the entry fails the
|
|
50
|
+
guard. The nine known-broken packages are recorded there with error counts
|
|
51
|
+
(`@object-ui/runner` has no `tsconfig.json` at all), tracked as follow-ups.
|
|
52
|
+
- New `Type Check` CI job runs the coverage guard first (instant, no install),
|
|
53
|
+
then `pnpm type-check`.
|
|
54
|
+
|
|
55
|
+
Both halves were proven to fail before being trusted: the guard was exercised in
|
|
56
|
+
all four of its failure modes, and re-introducing the `maplibre-gl` import turns
|
|
57
|
+
the job red again, as does a fresh error injected into `plugin-ai` — a package
|
|
58
|
+
that had no type checking whatsoever before this change.
|
|
59
|
+
|
|
3
60
|
## 16.1.0
|
|
4
61
|
|
|
5
62
|
## 16.0.0
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@object-ui/create-plugin",
|
|
3
|
-
"version": "
|
|
3
|
+
"version": "17.1.0",
|
|
4
4
|
"description": "CLI tool to scaffold ObjectUI plugins",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"license": "MIT",
|
|
@@ -15,9 +15,9 @@
|
|
|
15
15
|
"LICENSE"
|
|
16
16
|
],
|
|
17
17
|
"dependencies": {
|
|
18
|
-
"chalk": "^
|
|
18
|
+
"chalk": "^6.0.0",
|
|
19
19
|
"commander": "^15.0.0",
|
|
20
|
-
"fs-extra": "^11.
|
|
20
|
+
"fs-extra": "^11.4.0",
|
|
21
21
|
"prompts": "^2.4.2"
|
|
22
22
|
},
|
|
23
23
|
"devDependencies": {
|
|
@@ -56,6 +56,7 @@
|
|
|
56
56
|
},
|
|
57
57
|
"scripts": {
|
|
58
58
|
"build": "tsup",
|
|
59
|
+
"type-check": "tsc --noEmit",
|
|
59
60
|
"dev": "tsup --watch",
|
|
60
61
|
"test": "vitest run",
|
|
61
62
|
"lint": "eslint ."
|