Trouble integrating Astro plugin (@forastro/astro-nx) into Nx workspace + questions on publishing and Nx 20+ compatibility

[louiss0]

Title: Trouble integrating Astro plugin (@forastro/astro-nx) into Nx workspace + questions on publishing and Nx 20+ compatibility

Hi Nx team,

I’m running into issues trying to use the Astro plugin (@forastro/astro-nx) within a minimal Nx workspace. I prepared a small reproduction and collected environment details and logs below. I’d also like guidance on the correct way to publish a community plugin so it remains compatible with Nx 20+.

What I’m trying to do

• Create a fresh Nx workspace
• Install @forastro/astro-nx and generate an Astro app via a generator
• Run Nx targets (dev/build/preview/check) provided by the plugin

Observed behavior

• Nx cannot resolve generators from the plugin (see logs below).
• Running nx g @forastro/astro-nx:app fails with: "The "@forastro/astro-nx" package does not support Nx generators."
• This suggests Nx cannot find a generators.json or plugin.json wiring (even though the published package claims generators/ executors in its files).

Steps to reproduce (minimal)

1. Create workspace (package manager: pnpm)

   pnpm dlx create-nx-workspace@21.3.11 astro-nx-repro --preset=apps --nxCloud=skip --packageManager=pnpm --no-interactive

2. Enter the workspace and install plugin + deps

   pnpm --dir astro-nx-repro add -D @forastro/astro-nx astro @nx/workspace @nx/js @nx/devkit vitest

3. Try to generate an app

   cd astro-nx-repro
   pnpm nx g @forastro/astro-nx:app demo-app --no-interactive --verbose

Expected behavior

• The generator should be found and scaffold a new Astro application (project.json, astro.config, src/, etc.).
• Plugin executors should be invokable (e.g., @forastro/astro-nx:dev, :build, :preview, :check).

Environment

• OS: Linux/Pop!_OS
• Node: v20.18.0
• pnpm: 10.11.0
• Nx: 21.3.11
• Astro: ^5.x

nx report (from logs/nx-report.txt)

$(cat logs/nx-report.txt)

Failure logs (from logs/generator.log)

$(cat logs/generator.log)

Tools used in the project

• Monorepo manager: Nx
• Test runner: Vitest
• Bundler: esbuild/tsup
• Linter: ESLint
• Formatter: Prettier
• OS: Linux/Pop!_OS

How the package.json is built (plugin authoring context)

• My monorepo builds package.json programmatically and validates with zod. It enforces:
  • scripts.build format (regex-checked)
  • type: "module"
  • publishConfig.access: "public"
  • strict exports mapping
• Build transforms:
  • Strips leading ./src in exports
  • Converts .ts -> .js for import fields
• The plugin package ships:
  • plugin.json
  • executors.json
  • generators.json
  • compiled outputs under src/
  • README.md, LICENSE, CHANGELOG.md

Questions for the Nx team

1. How should a community plugin be structured so Nx 20+ can detect its generators and executors reliably (required files, package.json fields, exports)?
2. Are there known gotchas around ESM-only plugins ("type": "module") for Nx plugin resolution?
3. Should plugin.json, generators.json, and executors.json live at top-level and/or be explicitly exposed via files/exports so Nx finds them when installed from npm?
4. Recommended publishing/testing process to ensure Nx 20+ compatibility?
5. Any schema/validation guidance to prevent breaking changes across Nx majors?

Additional info

• OS: Linux/Pop!_OS
• Repro repo: https://github.com/louiss0/astro-nx-repro

Thanks!

[louiss0]

It was my fault I forgot about this. I managed to fix it