Issue: ESLint Dependencies in Shared Node Module
Unanswered
Argentine ant posted this in #help-forum
Argentine antOP
I have a Next.js 14 project using a shared ESLint configuration hosted in a private GitLab node module. The shared module lists eslint and its plugins in dependencies.
Question:
Should ESLint and plugins be listed in peerDependencies and devDependencies in the shared module instead of dependencies, to avoid unnecessary inclusion in production builds while ensuring proper functionality?
Context:
The shared module's ESLint config works as expected in the project.
Concerned about bundling and best practices for production.
Looking for guidance on the correct dependency setup for this scenario.
Question:
Should ESLint and plugins be listed in peerDependencies and devDependencies in the shared module instead of dependencies, to avoid unnecessary inclusion in production builds while ensuring proper functionality?
Context:
The shared module's ESLint config works as expected in the project.
Concerned about bundling and best practices for production.
Looking for guidance on the correct dependency setup for this scenario.