Repository navigation
chore(deps-dev): update dependency jsdom to v30.0.1 - #1340
Merged
Merged
Conversation
Contributor
|
Deploy preview for adp-cost-calculator ready!
Deployed with vercel-action |
Contributor
|
Deploy preview for remote-flows ready!
Deployed with vercel-action |
2 tasks done
renovate
Bot
force-pushed
the
renovate/jsdom-30.x
branch
2 times, most recently
from
September 21, 2026 07:52
7dba40c to
0867289
Compare
gabrielseco
added a commit
that referenced
this pull request
Sep 21, 2026
Renovate's lockfile-only install (used for most dependency bumps) never populates node_modules/.bin, so the repo's `prepare` script (`npm run build` -> tsdown) fails with "tsdown: command not found", aborting the whole update. Renovate then commits only the package.json bump without a matching package-lock.json, which breaks `npm ci` in CI for every subsequent PR check. This previously went unnoticed because Renovate reuses a cached node_modules across runs, and a working tsup binary was already present from earlier installs. The tsup -> tsdown migration (#1325) reset that cache, and the next two dependency PRs (#1339, #1340) hit the bug for the first time. ignoreScripts tells Renovate to skip lifecycle scripts during its own lockfile computation. It has no effect on real CI or local installs, which still run prepare/build as normal. Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
renovate
Bot
force-pushed
the
renovate/jsdom-30.x
branch
3 times, most recently
from
September 21, 2026 09:02
201e55e to
a949086
Compare
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit a949086. Configure here.
1 of 2 tasks
gabrielseco
added a commit
that referenced
this pull request
Sep 22, 2026
…1346) npm 12 (Renovate's hosted runner) changed allow-remote's default from all to none. @tailwindcss/oxide's wasm32-wasi optional fallback declares bundleDependencies, which forces npm to download/unpack that tarball to re-resolve the tree on any package.json edit — npm 12 now refuses that as a "remote" fetch even though it comes straight from registry.npmjs.org: npm error code EALLOWREMOTE npm error Fetching packages of type "remote" have been disabled npm error Refusing to fetch ".../@tailwindcss/oxide-wasm32-wasi-4.2.4.tgz" This repo's Renovate npmrc already forces `include=optional` (to keep every platform's optional binaries in the lockfile for devs/CI on other platforms), which is why Renovate touches this package at all. Adding allow-remote=all to that same Renovate-only npmrc unblocks the fetch. Same scoping as #1341's ignoreScripts: it has no effect on real CI or local installs. Seen failing on #1340 (jsdom bump) after #1341 fixed the earlier tsdown/prepare-script issue. Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
renovate
Bot
force-pushed
the
renovate/jsdom-30.x
branch
from
September 22, 2026 09:05
a949086 to
35ea859
Compare
Contributor
📦 Bundle Size Report
Size Limits
Largest Files (Top 5)
View All Files (74 total)
✅ Bundle size check passed |
gabrielseco
approved these changes
Sep 22, 2026
Contributor
📊 Coverage Report⚪ Coverage unchanged
Detailed BreakdownLines Coverage
Statements Coverage
Functions Coverage
Branches Coverage
✅ Coverage check passed |
gabrielseco
approved these changes
Sep 22, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
30.0.0→30.0.1Release Notes
jsdom/jsdom (jsdom)
v30.0.1Compare Source
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.
Note
Low Risk
Dev-only patch dependency for the test runner; no production or runtime behavior changes.
Overview
Bumps the jsdom dev dependency from
30.0.0to30.0.1inpackage.jsonand refreshespackage-lock.jsonaccordingly.jsdom is used as the DOM environment for Vitest; this is a patch release with updated transitive deps (e.g.
@asamuzakjp/dom-selector,undici). No source or test config changes are included.Reviewed by Cursor Bugbot for commit 35ea859. Bugbot is set up for automated code reviews on this repo. Configure here.