Skip to content

Bump strnum to 2.4.2 - #41

Merged
ww-mw merged 1 commit into
mainfrom
bump-strnum
Oct 3, 2026
Merged

ww-mw merged 1 commit into
mainfrom
bump-strnum

Conversation

@ww-mw

@ww-mw ww-mw commented Oct 3, 2026

Copy link
Copy Markdown
Member

Lockfile-only patch bump. 2.4.2 is in range of every "^2.4.1" asking for it, so there is no package.json edit and no overrides entry.

This is the copy that ships: core's prebuilt dist/ imports strnum rather than bundling it (import toNumber from 'strnum' in dist/datamodel/parser/DictionaryXmlFast.js), so esbuild resolves it out of this repo's node_modules when it inlines core into dist/extension.js. The two repos' bumps are therefore independent — core's is mathworks/data-explorer-core#64 — and neither needs a core release or a pin bump to take effect.

resolved rewritten back to registry.npmjs.org after the install; integrity is content-based and unaffected. npm run check:leak confirms all 646 resolutions.

Local run note, for the record: npm test on this Mac flakes rowBuilder.test.ts > builds every row instead of overflowing the argument limit — Test timed out in 5000ms at 5683ms for a 200,000-row build. It passes in isolation in 1.4s, and passed in the full suite an hour ago on #39; it is machine load, not this bump. CI is the gate.

The copy esbuild inlines into dist/extension.js: core's dist imports
strnum rather than bundling it (`import toNumber from 'strnum'` in
DictionaryXmlFast.js), so it is THIS lockfile that decides which version
ships, not core's — the two repos' bumps are independent, and core's own
is PR mathworks/data-explorer-core#64. 2.4.2 is in range of every
"^2.4.1" asking for it, so the lockfile alone moves.

The resolved URL was rewritten back to registry.npmjs.org after the
install; integrity is content-based and unaffected, and check:leak
confirms all 646 resolutions.
@ww-mw
ww-mw merged commit 7e3a37f into main Oct 3, 2026
4 checks passed
@ww-mw
ww-mw deleted the bump-strnum branch October 3, 2026 07:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant