fix(cli): set current working directory before scaffolded npm init #1150
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.
Closes #1142
Summary of changes:
In my testing of production, running
npm init patternlab
prompts you to choose a directory,If you choose to specify a directory (assuming to create a new one, in this case, we check for the presence of a
package.json
but then don't use that same path to runnpm init
if one is not found. Sure enough, thepackage.json
is created in the calling directory, not the new one.This change Attempts to set current working directory prior to project init.
I tried getting the scaffold tests to work but could not in limited time.