eslint-plugin-node
eslint-plugin-node copied to clipboard
Rule `node/no-unpublished-import` should not be enabled for private packages
If package.json file has "private" set to true, it will restrict the package from being published to the registry. Therefor having node/no-unpublished-import rule enabled does not make sense.
I agree, and the same observation applies to node/no-unpublished-require.
Happy to make a PR if this should be addressed ;)
Is this still in discussion ?
At least, I'm using those rules for private packages as well.
Could be an option instead?
It is so obvious to me that I can't wait when this will be done. @mysticatea can you show examples of mistakes that you want to prevent with this rule in a private package?
Can we merge this in yet? Has been 5 years since this was opened?
can this issue be closed now?
It has been merged into the maintained for, eslint-plugin-n: https://github.com/eslint-community/eslint-plugin-n/pull/57