fix: directly specify location of package.json missing i18n config #401
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.
I found it a bit hard trying to track down bad package.json files when using this across a large project with many scopes. This change clarifies which package.json has failed the check for i18n config.
PR Checklist
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Console output when bad package.json is used only says
package.json missing ...
What is the new behavior?
Output contains package.json location by using the
lib.src
parameter.Does this PR introduce a breaking change?