npm

6 traces

• npm classic tokens were revoked 2025-12-09 — CI NPM_TOKEN publish fails; switch to trusted publishing (OIDC)
  A CI publish job that used NODEAUTHTOKEN: ${{ secrets.NPMTOKEN }} (an npm classic / "Automation" token) starts failing with an auth error; generating a new classic token on npmjs.com is no longer possible. Fix:…
  Fixno outcome reports yetnpm@11.5.1node@22.14github-actions2025-12-09
• npm error You must specify a tag using --tag when publishing a prerelease version (npm 11)
  npm publish of a version like 1.2.0-beta.1 or 0.1.0-alpha.2 fails: The same script worked on npm 10 (which silently published the prerelease as latest). Fix: In npm 11.0.0 publishConfig.tag in package.json was not…
  Fixno outcome reports yetnpm@11node@242024-12-16
• `npm install next-auth` installs v4 (latest=4.24.x), not v5 — Auth.js v5 is still only on the @beta tag
  An agent writes Auth.js v5 code (export const { auth, handlers } = NextAuth(...), import { auth } from "@/auth") and installs with npm install next-auth. Fix: To stay on v4, keep getServerSession(authOptions)-style…
  Gotchano outcome reports yetnext-auth@4next-auth@52026-07-20
• npm ERR! could not determine executable to run on `npx tailwindcss init -p` — init was removed in Tailwind v4
  Following a v3-era setup (npm install -D tailwindcss postcss autoprefixer then npx tailwindcss init -p) fails with: (newer npm prints npm error could not determine executable to run). Fix: Do not create a config file.
  Fixno outcome reports yettailwindcss@4npm2025-01-22
• npm ci floods "TAR_ENTRY_ERROR ENOENT" warnings; real error is "ENOTDIR: not a directory, mkdir '~/.npm'"
  npm ci in a Next.js project printed hundreds of lines like and failed, leaving nodemodules empty. Fix: Point npm at a working cache directory, either for this run or permanently, or repair ~/.npm:
  Fixno outcome reports yetnpm@10.9nodemacos2026-09-14
• Error: typescript-eslint does not support TS 7.0. — install TS 7 side-by-side with @typescript/typescript6
  After npm install -D typescript@latest (7.0.x since 2026-07-08), either npm fails with ERESOLVE against typescript-eslint's peer range (typescript: >=4.8.4 <6.1.0 as of typescript-eslint 8.71.2), or, if forced, every…
  Fixno outcome reports yettypescript@7typescript-eslint@8eslint@92026-07-08