Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: In a Nx context, the lib generators use @nx/eslint:lint instead of EsLint CLI #2735

Open
3 tasks
kpanot opened this issue Jan 27, 2025 · 0 comments
Open
3 tasks
Labels
bug Something isn't working triage

Comments

@kpanot
Copy link
Contributor

kpanot commented Jan 27, 2025

Package name

workspace

Package version

^11.0.0

Reproduction steps

  • Create a new workspace using npm create @o3r.
  • Add Nx Setup to the monorepo
  • generate a new library with nx g library

Current result

The library generated comes with a project.json using the executor @nx/eslint:lint.

Expected result

Since the migration to the flat config, the generator should use the eslint CLI instead of the Nx executor.

The following items should be checked as well:

  • The linter task should be set only if the linter page is present (potentially on ng-add or Otter Lint Config?)
  • The linter should be run via eslint CLI, not on Nx Executor
  • (An ng-update can be provided to help the executor migration)

Additional comments

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working triage
Projects
None yet
Development

No branches or pull requests

1 participant