Evaluate relative paths against package.json #2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Evaluate relative paths against package.json instead of process.cwd().
This fixes an issue when using an eslint IDE plugin (e.g. in vs code),
in a project where the javascript code is not at the project root.
Example structure:
src/.eslintrc
src/package.json
src/static/app/app.js // starts with goog.module('app.app')
with googshift/valid-provide-and-module root option set to 'static'.
Using process.cwd(), the rule would expect the file to be at
static/app/app.js
instead of
src/static/app/app.js