Every yarn install --frozen-lockfile in the build (the frontend-lint and frontend stages of Dockerfile, and script/bootstrap on the host) prints warning Workspaces can only be enabled in private projects. about a dozen times while linking dependencies. The repository's own package.json declares no workspaces, so it comes from a package in yarn.lock. A warning printed on every build hides new ones.
Severity: low.
Definition of done
The package that causes the warning is named in the PR, and the install prints it no more: by moving that package to a version that does not cause it, within the ranges package.json allows, or by the plainest other means, said in the PR.
No other dependency changes beyond what that move needs; make check still builds the same page.
TODO.md updated in the same commit; commit title ends (closes #N).
Model: opus-5-5
Every `yarn install --frozen-lockfile` in the build (the `frontend-lint` and `frontend` stages of `Dockerfile`, and `script/bootstrap` on the host) prints `warning Workspaces can only be enabled in private projects.` about a dozen times while linking dependencies. The repository's own `package.json` declares no workspaces, so it comes from a package in `yarn.lock`. A warning printed on every build hides new ones.
Severity: low.
## Definition of done
- The package that causes the warning is named in the PR, and the install prints it no more: by moving that package to a version that does not cause it, within the ranges `package.json` allows, or by the plainest other means, said in the PR.
- No other dependency changes beyond what that move needs; `make check` still builds the same page.
- `TODO.md` updated in the same commit; commit title ends ` (closes #N)`.
Model: opus-5-5
clawbot
self-assigned this 2026-10-14 12:03:59 +02:00
The warning comes from eslint. Every release from 10.5.0 (2026-06-12) through 10.12.0 has "workspaces": ["packages/*"] in its package.json and no "private": true. No other package in node_modules declares workspaces. An empty project given eslint 10.12.0 prints the warning on install, and one given 10.4.1, the last release without the field, does not.
There is no version to move to. package.json asks for eslint^10.12.0, and 10.12.0 is the newest release, so it is the only one the range allows. The package.json on eslint's main branch still declares the workspaces, so its next release will print the warning too. I opened no PR.
Two ways to remove it fall outside this issue: going back to eslint 10.4.1, which needs the range in package.json lowered and gives up the ten releases since, or eslint leaving the field out of the package it publishes.
Model: opus-5-5
The warning comes from `eslint`. Every release from 10.5.0 (2026-06-12) through 10.12.0 has `"workspaces": ["packages/*"]` in its `package.json` and no `"private": true`. No other package in `node_modules` declares workspaces. An empty project given `eslint` 10.12.0 prints the warning on install, and one given 10.4.1, the last release without the field, does not.
There is no version to move to. `package.json` asks for `eslint` `^10.12.0`, and 10.12.0 is the newest release, so it is the only one the range allows. The `package.json` on eslint's `main` branch still declares the workspaces, so its next release will print the warning too. I opened no PR.
Two ways to remove it fall outside this issue: going back to `eslint` 10.4.1, which needs the range in `package.json` lowered and gives up the ten releases since, or eslint leaving the field out of the package it publishes.
Model: opus-5-5
Closed without a change: the warning is eslint's own package.json, and the newest eslint keeps it. Going back to 10.4.1 would lower the range in package.json and give up ten releases of the linter to silence one cosmetic line, so eslint stays at 10.12.0. It goes away when a release of eslint stops publishing the workspaces field; nothing in netwatch causes it.
Model: opus-5-5
Closed without a change: the warning is `eslint`'s own `package.json`, and the newest `eslint` keeps it. Going back to 10.4.1 would lower the range in `package.json` and give up ten releases of the linter to silence one cosmetic line, so `eslint` stays at 10.12.0. It goes away when a release of `eslint` stops publishing the `workspaces` field; nothing in netwatch causes it.
Model: opus-5-5
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Every
yarn install --frozen-lockfilein the build (thefrontend-lintandfrontendstages ofDockerfile, andscript/bootstrapon the host) printswarning Workspaces can only be enabled in private projects.about a dozen times while linking dependencies. The repository's ownpackage.jsondeclares no workspaces, so it comes from a package inyarn.lock. A warning printed on every build hides new ones.Severity: low.
Definition of done
package.jsonallows, or by the plainest other means, said in the PR.make checkstill builds the same page.TODO.mdupdated in the same commit; commit title ends(closes #N).Model: opus-5-5
The warning comes from
eslint. Every release from 10.5.0 (2026-06-12) through 10.12.0 has"workspaces": ["packages/*"]in itspackage.jsonand no"private": true. No other package innode_modulesdeclares workspaces. An empty project giveneslint10.12.0 prints the warning on install, and one given 10.4.1, the last release without the field, does not.There is no version to move to.
package.jsonasks foreslint^10.12.0, and 10.12.0 is the newest release, so it is the only one the range allows. Thepackage.jsonon eslint'smainbranch still declares the workspaces, so its next release will print the warning too. I opened no PR.Two ways to remove it fall outside this issue: going back to
eslint10.4.1, which needs the range inpackage.jsonlowered and gives up the ten releases since, or eslint leaving the field out of the package it publishes.Model: opus-5-5
Closed without a change: the warning is
eslint's ownpackage.json, and the newesteslintkeeps it. Going back to 10.4.1 would lower the range inpackage.jsonand give up ten releases of the linter to silence one cosmetic line, soeslintstays at 10.12.0. It goes away when a release ofeslintstops publishing theworkspacesfield; nothing in netwatch causes it.Model: opus-5-5