@xmbl/simulator 0.1.13 → 0.1.14
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 +25 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,30 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 0.1.14
|
|
4
|
+
|
|
5
|
+
### Patch Changes
|
|
6
|
+
|
|
7
|
+
- **Every prebuilt binary was broken; all four causes are fixed.** `gh release list` returned
|
|
8
|
+
nothing for any version of this repo. The release workflow gated its artifacts job on the
|
|
9
|
+
crates.io job, which had no token from the first tag onward, so packaging was SKIPPED on every
|
|
10
|
+
release ever cut — and underneath that, all three packaging jobs would have failed anyway:
|
|
11
|
+
|
|
12
|
+
- **desktop** — `packages/desktop-app` is `"type": "module"`, so the CommonJS
|
|
13
|
+
`electron-builder.config.js` threw on load and electron-builder fell back to a `build` key that
|
|
14
|
+
does not exist: appId, targets, output directory and file globs were all dead. Renamed `.cjs`
|
|
15
|
+
and passed explicitly. `electron` was also a runtime dependency (electron-builder refuses to
|
|
16
|
+
package at all) and npm workspaces hoist it out of the project, so the version could not be
|
|
17
|
+
computed. Both fixed, with the author/maintainer fields `deb` and `AppImage` require, both
|
|
18
|
+
target architectures for mac/win/linux, and the `deb` target the workflow always globbed for.
|
|
19
|
+
- **web** — `apps/app-builder/vite.config.js` aliased `buffer` into the app's own
|
|
20
|
+
`node_modules`, which npm workspaces hoist to the root, so `vite build` died with ENOENT. Two
|
|
21
|
+
Vue templates also carried `:id="@xmbl/identity"`, which is not a JavaScript expression.
|
|
22
|
+
- **extension** — `@xmbl/lng`'s exports map had no `browser` condition, so bundlers resolved the
|
|
23
|
+
node entry, which reads its own `package.json` through `node:fs` at module scope. **`@xmbl/lng`
|
|
24
|
+
now declares `browser` -> `dist/lng.browser.js` in `exports`**, which is the one change in this
|
|
25
|
+
release that affects consumers: a bundler targeting the browser now gets the prebuilt bundle
|
|
26
|
+
(same export surface, including `VERSION`) instead of failing on `node:fs`.
|
|
27
|
+
|
|
3
28
|
## 0.1.13
|
|
4
29
|
|
|
5
30
|
### Patch Changes
|