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

Add require-module to npmPackageJsonLintConfig in package.json #14399

Closed
wants to merge 1 commit into from

Conversation

ntwb
Copy link
Member

@ntwb ntwb commented Mar 13, 2019

Description

Follow up to #14388 to add require-module to the npmPackageJsonLintConfig in package.json

How has this been tested?

Screenshots

Types of changes

Checklist:

  • My code is tested.
  • My code follows the WordPress code style.
  • My code follows the accessibility standards.
  • My code has proper inline documentation.
  • I've included developer documentation if appropriate.

@ntwb ntwb added the [Type] Build Tooling Issues or PRs related to build tooling label Mar 13, 2019
@ntwb ntwb requested review from gziolo and aduth March 13, 2019 04:37
@ntwb
Copy link
Member Author

ntwb commented Mar 13, 2019

13 packages affected:

[1] ./packages/babel-plugin-import-jsx-pragma/package.json
[1] ✖ require-module - node: module - module is required
[1] 1 error
[1] 0 warnings
[1] 
[1] ./packages/babel-preset-default/package.json
[1] ✖ require-module - node: module - module is required
[1] 1 error
[1] 0 warnings
[1] 
[1] ./packages/block-serialization-spec-parser/package.json
[1] ✖ require-module - node: module - module is required
[1] 1 error
[1] 0 warnings
[1] 
[1] ./packages/browserslist-config/package.json
[1] ✖ require-module - node: module - module is required
[1] 1 error
[1] 0 warnings
[1] 
[1] ./packages/docgen/package.json
[1] ✖ require-module - node: module - module is required
[1] 1 error
[1] 0 warnings
[1] 
[1] ./packages/e2e-tests/package.json
[1] ✖ require-module - node: module - module is required
[1] 1 error
[1] 0 warnings
[1] 
[1] ./packages/eslint-plugin/package.json
[1] ✖ require-module - node: module - module is required
[1] 1 error
[1] 0 warnings
[1] 
[1] ./packages/is-shallow-equal/package.json
[1] ✖ require-module - node: module - module is required
[1] 1 error
[1] 0 warnings
[1] 
[1] ./packages/jest-preset-default/package.json
[1] ✖ require-module - node: module - module is required
[1] 1 error
[1] 0 warnings
[1] 
[1] ./packages/library-export-default-webpack-plugin/package.json
[1] ✖ require-module - node: module - module is required
[1] 1 error
[1] 0 warnings
[1] 
[1] ./packages/npm-package-json-lint-config/package.json
[1] ✖ require-module - node: module - module is required
[1] 1 error
[1] 0 warnings
[1] 
[1] ./packages/postcss-themes/package.json
[1] ✖ require-module - node: module - module is required
[1] 1 error
[1] 0 warnings
[1] 
[1] ./packages/scripts/package.json
[1] ✖ require-module - node: module - module is required
[1] 1 error
[1] 0 warnings
[1] 
[1] Totals
[1] 13 errors
[1] 0 warnings

@gziolo
Copy link
Member

gziolo commented Mar 13, 2019

Is there any way for a package to mark that it is not using module at all. It might be all correct that they don't provide module because they are never transpiled.

@ntwb
Copy link
Member Author

ntwb commented Mar 13, 2019

There is not, currently, I've added a comment to tclindner/npm-package-json-lint#93 (comment) which is seeking to add exceptions for another rule, and as noted in my comment there, there are quite possibly other rules that on occasion exceptions would be handy.

@aduth
Copy link
Member

aduth commented Apr 24, 2019

Would it be fair to consider this as blocked by tclindner/npm-package-json-lint#93 ?

Otherwise, how can we move forward here?

@aduth aduth added the [Status] Blocked Used to indicate that a current effort isn't able to move forward label Apr 24, 2019
@aduth
Copy link
Member

aduth commented Mar 10, 2020

tclindner/npm-package-json-lint#93 appears to have been addressed. Should this be updated now?

@aduth aduth added [Status] Stale Gives the original author opportunity to update before closing. Can be reopened as needed. and removed [Status] Blocked Used to indicate that a current effort isn't able to move forward labels Mar 10, 2020
@youknowriad
Copy link
Contributor

Hi There! I've triaging PRs today and it seems this one is stale. I'm going to close now but please consider reopening if you have some time to refresh it. Thanks.

@youknowriad youknowriad deleted the try/require-module branch May 27, 2020 17:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Status] Stale Gives the original author opportunity to update before closing. Can be reopened as needed. [Type] Build Tooling Issues or PRs related to build tooling
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants