Repository navigation
test(deps): update dependency nub to v0.10.0 (main) - #8232
Merged
Merged
Conversation
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:
0.9.7→0.10.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
nubjs/nub (nub)
v0.10.0: Nub 0.10.0Compare Source
Nub 0.10.0 brings dependency build scripts and
--filterin line with pnpm 12, writes pnpm lockfiles that pnpm accepts in more layouts, and backfillsutil.debounce,util.throttleand theJSON.parseoptions proposal.Dependency build scripts
An install that meets a build script nobody has approved now fails, as under pnpm 12. It fails last, once
node_modulesis linked and the approved builds and the project's own scripts have run. Global installs andnubxstay non-strict.nub approve-builds '!pkg'and--allow-build='!pkg'record a denial, and--allow-build=pkgrefuses a package the project denies. An explicitfalseoutranksdangerouslyAllowAllBuilds.dangerouslyAllowAllBuildsandstrictDepBuildsare read from.npmrc, the environment and, in a pnpm project,pnpm-workspace.yaml.nub rebuildnub rebuild,nub ignored-buildsandnub approve-buildsread the same approvals asnub install, workspace members' included.<name>@git+<repository>or the same key with#<commit>. A bare name,name@versionor*does not approve one, and a denial installs it unbuilt.rimraf@github:isaacs/rimraf#v6.1.3is now built. It linked with nodist/. The build no longer needscp, which stock Windows lacks.installaddspreprepareandpostprepare,removeruns the uninstall stages, and--prodskips thepreparefamily.Workspace filters
Nub now uses pnpm 12's selector grammar and directory globs on every workspace command, including
nub run(#1056).install,removeandupdateprintScope: 0 of N workspace projects, andnub cistill cleansnode_modulesfirst, as pnpm's does.run,exec,addandtestdrop the root from a selection that names no project. Other commands keep it.recursiveInstallpnpm-workspace.yamlin a pnpm project.--filter-prod,-Cand--dirwork there.nub lsin a memberLockfile compatibility
shared-workspace-lockfile=false, a member's lockfile matches pnpm 10's bytes on the tested workspaces. pnpm's--frozen-lockfilerejected the old form.nub install --frozen-lockfilepasses on a tree Nub or pnpm 10 wrote, and a plain install keeps a member's locked versions. It failed on the first and re-resolved on the second.nub rebuildfinds a member's packages in the root store. It built nothing and exited 0.pnpm-lock.yamlrecords a pinned pnpm in its leading document, so pnpm 11 and 12 accept Nub's lockfile under--frozen-lockfile, including afternub pm use pnpm.pnpm-lock.yamllink:./xis writtenlink:xandfile:./xis writtenfile:x, and emptypackages:andsnapshots:are omitted. A package spelled with./relinks on its first install after upgrading.file:dependency outside the workspacefile:directory above the workspace root installs undernub ciand--frozen-lockfile. It failed withis not a directory.package-lock.jsondevandoptional. It wasdevOptional.nub.lock, andbun.lockrecords peers as bun writes them.nub update -rraises a^or~catalog entry to the version it resolved, and a catalog-only lockfile change is written instead of skipped.catalog:catalog:dependency by its reference, as under pnpm.Package manager
nub packandnub publishmain, or a symlinked README, put that file in the tarball.workspace:specsworkspace:andcatalog:specs and applypublishConfig. The specs shipped verbatim, which made the package uninstallable.nub updateat a workspace rootpatchedDependenciesnub patch-commitnub patchresolves its target through the lockfile..npmrc/etc/resolver/*and Windows NRPT apply.node_modules. It removed the tree before resolving.--offlinefile:dependencies on macOSfile:dependency at the same relative path get their own files. They shared whichever installed first, and a tarball rebuilt in place stayed stale.file:path is ejected into the project. The link dangled andrequirefailed withCannot find module.EBADF.--allow-similar-nameand--allow-new-nameeach clear their own check, and every refusal names its flag andallowedUnpopularPackages.tscstays withtypescriptwhentypescript5is also installed.^3.0.0,3.1.0and>=2keep the shared store. Only a spec that may select a 3.0.0 prerelease gets a project-local store.nub pm shimpnpmandpnpxshims run pnpm 12. They failed withSyntaxError: Unexpected identifier 'is'.nub pm shimprojectsnpm loginpass through to the system manager instead of being refused.nub pm use nubRuntime
util.debounce,util.throttle@nubjs/types.JSON.parseoptionsJSON.parse(text, { freeze, preferNullPrototype })is polyfilled from the Stage 2.7 proposal, and typed in@nubjs/types.NaN,-0, dates and own__proto__keys. A TOML date is aDate, and a TOML integer past 2^53 is aBigInt. It threw on import.UV_THREADPOOL_SIZEprocess.envbefore the first pool use sizes the pool, as under Node. Nub's preload had already built the pool.require()of a replaced package@js-temporal/polyfill,urlpattern-polyfillandabort-controllerload the installed package. They failed withENOENTon Node 22.15+.internal/fileon Node 20+.node_moduleslink failed before starting.varlock run --path ./configexited 1.--test=<value>,--watch=<value>,--watch_pathand a watch flag inNODE_OPTIONSstay out of the children they start, which could recurse without end.nodeOptionsinnub.jsoncrefuses a watch flag.Node discovery and provisioning
latestand other aliases.nvmrcoflatestfailed with a 404 once nodejs.org listed a 27.0.0 alpha.nodethat hands the launch back to Nub, or links back to it, is skipped. Any chain of Nub processes stops at 64 withERR_NUB_LAUNCH_LOOP.Install and upgrade
nub upgradeunder misemise upgrade --bump nub. It took the npm channel, which planted a second global copy.packslip.sigstore.json, a signed manifest of its archives, so mise can install Nub straight from the release.Docs, testing and internals
macos-15after GitHub retiredmacos-14(4a599b6).What's Changed
nubcondition as an export condition, not a runtime key by @colinhacks in #990New Contributors
Full Changelog: nubjs/nub@v0.9.7...v0.10.0
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ 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.