Skip to content

Conversation

mattheu
Copy link
Member

@mattheu mattheu commented Aug 3, 2022

We are using npm-package-json-lint to check that our package.json files comply with certain rules.

One of these rules is configured so that you are not allowed to use devDependencies in the packages, but it's OK at the top-level. However this test fails because we have devDependencies in the eslint config package.

Seems to me that we should just disable this rule. I'm not sure why it has ever passed TBH.

@ntwb
Copy link
Contributor

ntwb commented Aug 8, 2022

This is because the devDependencies need to be moved from the ESLint package to the root package.json

This just hasn't happened yet and is why this rule is only set to warning which is why CI runs currently pass

"prefer-no-devDependencies": "warning",

E.g. via https://app.travis-ci.com/github/humanmade/coding-standards/jobs/578616221#L262-L270

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants