Repository navigation
chore(deps): update dependency nub to v0.11.1 - #81
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/nub-0.x
branch
from
November 7, 2026 21:44
ee52e5c to
f0097d1
Compare
renovate
Bot
force-pushed
the
renovate/nub-0.x
branch
from
November 14, 2026 01:36
f0097d1 to
410c813
Compare
renovate
Bot
force-pushed
the
renovate/nub-0.x
branch
from
November 17, 2026 02:27
410c813 to
9974d11
Compare
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.
Note
This PR body was truncated due to platform limits.
This PR contains the following updates:
0.9.6→0.11.1Release Notes
nubjs/nub (nub)
v0.11.1: Nub 0.11.1Compare Source
Nub 0.11.1 provisions Yarn 2+ (Berry) pins without a committed release, refreshes the bundled packageExtensions database, and starts on Node builds that have removed
module.register().Yarn Berry pins
A
packageManagerordevEngines.packageManagerpin to Yarn 2 or later now downloads and runs like a pnpm, npm or Yarn 1 pin (#1124, fixes #1029). It failed with "yarn 2+ (Berry) requires a committed release" unless the project committed one and setyarnPath.@yarnpkg/cli-diston the configured registry, from 2.4.1 on. A committedyarnPathrelease still takes precedence.+sha512hash is checked againstyarn.js, the file Corepack hashes, so a pin either tool wrote verifies in both.nub pm use yarn@4andnub pm updatewrite Berry pins. Converting another manager's lockfile to Berry's format is refused.yarnonPATH, a Berryyarn.lockselects only Yarn releases that write that lockfile format.Fixes
@nubjs/extensions1.0.54.nitrono longer gainscroner,scule,ufoandunctx, which it now declares, and theobject.hasownandstring.prototype.codepointatrules are gone. Existing lockfiles do not change.module.register()--no-experimental-require-moduleon a Node 28 nightly, which removesmodule.register(), every process crashed at startup withTypeError: module_.register is not a function. Nub now prints one line saying its hooks are off and runs the program on plain Node.What's Changed
Full Changelog: nubjs/nub@v0.11.0...v0.11.1
v0.11.0: Nub 0.11.0Compare Source
Nub 0.11.0 preloads TypeScript 7.1 content mappers, adds
nub add --save-types, installs one copy of a package where pnpm does, and removes the canary channel. It also fixes a broad set of correctness bugs in the runtime, the package manager andnub run.Content mappers
TypeScript 7.1's content mappers type-check other file types, but TypeScript never runs them. Nub now preloads the
./registerexport of every package the tsconfig lists, with no--importand nonub.jsoncentry (#1082).{ // ... "contentMappers": [ { "package": "motherload", "extensions": [".toml", ".yaml"] } ] }extendsandreferencesare followed, the longest extension answers first, and an entry'soptionsreach its register inCONTENT_MAPPER_OPTIONS.Type packages on add
nub add --save-types <pkg>also saves the DefinitelyTyped package todevDependenciesfor each registry package whose installed version ships no types, picking the newest@typesrelease on that package's major (#1110, fixes #1016).A package with no
@typesrelease, or only a deprecated stub, printsskipped @types/<name>: <reason>. An@typesentry the project already lists is kept.Package manager
file:, URL or git package consumed with two sets of peers loads the right peer after a lockfile install. One entry served both consumers, with no error.requirefailed withCannot find module.file:andlink:packages read back fromnub.lockorpnpm-lock.yamlget the graph a fresh resolve gives. A root peer pinned to a tarball URL no longer fails every resolve after the first withERR_NUB_BLOCKED_EXOTIC_SUBDEP.nub addornub install <pkg>restorespackage.json, the lockfiles and the workspace yaml. The new dependency stayed inpackage.json.--fix-lockfilenub install --fix-lockfilerewrites the lockfile, keeping its pinned versions. It repairs apackage-lock.jsonwritten with the dev-optional flags 0.10.0 fixed.bun.locklocal pathsfile:directory and a hoisted tarball install undernub ciand--frozen-lockfile, and abun.lockNub writes spells local packages as bun does, whichbun install --frozen-lockfileaccepts.nub install --prod,--devand--no-optionaldownload only the dependencies they link. Every package in the graph was downloaded into the store.pnpm-workspace.yaml# commentafter a pattern or afterpackages:, and the flow formpackages: ['a/*', 'b/*'], are read. Each found no workspace members..npmrckeysscript-shell,ignore-scriptsornode-mirror:releasewins, as in npm. The first won.packageManagerpathspnpm@../npm/10.9.0, fails to resolve. It installed the other package into the store under the requested name.nub pm usenub pm use nubkeepscatalogandnohoistfrom an object-formworkspaces, andnub pm use pnpmkeeps the other keys underworkspaces.require('buffer/'), a directory with amain, a template-literalrequireandimport x = require()resolve as Node resolves them, and.d.mtsand.d.ctsfiles are not scanned.Running files
nub --permission --allow-addons app.jsstarts,--permissioninNODE_OPTIONSgets the same--allow-addonsmessage as the flag, and the last of--permissionand--no-permissiondecides, as in Node. The first two failed withERR_ACCESS_DENIEDon Nub's own runtime.nub app.js --permissionpasses--permissionto the program. It was read as Node's own flag..envPASSWORD="foo\$bar"loadsfoo$bar, and a variable that refers back to itself, such asA=x$A, expands that reference to nothing.engines.node: "20.11.0 || 22.1.0"matches those exact versions, avin a range is read as node-semver reads it, and a#comment in.nvmrcor.node-versionis read as nvm reads it.--import tsxruns on Node 24.11.1, 25.0 and 25.1. It failed withERR_METHOD_NOT_IMPLEMENTED.nub node installnodeshim onPATH, it installs only the version asked for.package.jsonandnode_modulesin the home folder no longer hang every run under it on macOS. The pre-run dependency scan skips a project rooted at the home folder and gives up after 500 ms.os.homedir()readsC:\Users\…inside a script and Nub's preload is injected once.Runtime
Intl.Locale#variantsis polyfilled and typed in@nubjs/types.Iterator.zipandIterator.zipKeyedclose every input on an early return or a failure. On Node 27, its native versions of these are used. A Test262 subset now runs against the polyfills.Promise.withResolvers,Iterator.from,URL.parse, theUint8Arraybase64 methods and 23 others have noprototypeand refusenew, like the builtins.Float16ArrayandURLPatternare non-enumerable,RegExp.escapeescapes lone surrogates, andErrorEventbefore Node 25 reads its fields from prototype getters.--experimental-web-workerWorkerglobal enabled, Nub keeps it and its worker scope instead of installing its polyfill.Workernub --max-old-space-size=4096 app.mjsno longer makes the globalWorkerthrowERR_WORKER_INVALID_EXEC_ARGV, and a worker that throwsnulldelivers itserrorevent.registerHooks--importthat callsmodule.registerHooks, such asamaro/strip, no longer makes every CommonJS file throwERR_INVALID_RETURN_PROPERTY_VALUE.Scripts and config
nub exec -r--sequential,--parallel--cwd=<dir>,--if-presentand--reporter-hide-prefixare accepted there. They failed withnode: bad option.PATHPATH.nub config setnub.jsoncinstead of replacing the link.nub initgit initin a subfolder of a repository.nubxpromptdlx.consent: "prompt"stays off.Install and upgrade
nub upgrade --canaryand--stable.nub-version: canaryin thesetup-nodeaction no longer installs.install.shlddon systems other than Alpine.setup-nodeaction.tool-versionsand an absolutepackage.jsonas anode-version-file, and.nvmrcand.node-versionas nvm reads them.Security
Nub's Rust network clients reject the compromised eMudhra certificate chains (#1019). JavaScript running under Node still relies on Node's own certificate store.
Docs, testing and internals
CONTRIBUTING.md, aSECURITY.mdand a code of conduct (#1116, #1115).nubbinary through Cargo, which keeps test executables in a different directory from Rust 1.100 (#1113).ci-fulllabel (#1104).86c1817).What's Changed
New Contributors
Full Changelog: nubjs/nub@v0.10.0...v0.11.0
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.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.