(fix/schematics): package.json generated scripts #785
Merged
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.
Documentation is right (https://scully.io/docs/scully-cmd-line/) for v1.0.0-beta.0, and says
--project
as the right way to launch those 2 scripts.PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
When adding scully capabilities (
ng add @scullyio/init
) to an existing Angular project (not default project) in a Nx mono-repo, when runningnpm run scully
, it simply fails, because it tries to launchscully --projectName=<projectName>
. Same fornpm run scully:serve
.Issue Number: N/A
What is the new behavior?
It works as expected.
Does this PR introduce a breaking change?
Other information
Tested on Angular 9.1.9 project on a Windows 10 machine.