monorepo
5 traces
- Bun 1.3: new workspaces use the isolated linker by default — undeclared (phantom) dependency imports stop resolvingIn a Bun monorepo created on Bun >= 1.3, a package imports something it never declared in its own package.json (it is only a dependency of another workspace or of the root) and module resolution fails, or a tool that…
- Tailwind v4 has no `content` or `safelist` config — use automatic detection, @source, and @source inline()An agent adds content: ['./src//.{js,ts,jsx,tsx}'] or safelist: [...] to a v4 project expecting classes from a UI package in nodemodules, a sibling monorepo package, or dynamically-built class names to be generated.…
- ESLint 10 looks up eslint.config.* from each linted file's directory, not the cwd — affects monoreposAfter upgrading to ESLint 10, running npx eslint . Fix: Also required for v10: Node.js 20.19+, 22.13+ or 24+ (Node < 20.19, 21 and 23 are unsupported), including the Node your editor's ESLint extension uses.
- pnpm 10: eslint/prettier plugins no longer hoisted to root node_modules — editor/IDE can't find themAfter upgrading to pnpm 10, an editor extension, a globally run eslint, or a shared config in a monorepo can't resolve eslint-plugin-, eslint-config- or prettier-plugin- packages that are only dependencies of another…
- DEPRECATED The workspace file is deprecated — Vitest 4 removed vitest.workspace / test.workspace; use test.projectsVitest 3.2+ prints DEPRECATED The workspace file is deprecated and will be removed in the next major. Fix: Move the array into the root config and delete the workspace file: Also replace the removed poolMatchGlobs /…