schematics generating a wrong npm command
See original GitHub issue🐞 Bug report
Description
If you create a new scully website, the npm run scully
script fails. If no one is working on it, please let me know so I can submit a fix.
🔬 Minimal Reproduction
On terminal:
ng new blog
ng add @scullyio/init
ng build --prod
npm run scully
💻Your Environment
Angular Version:
Angular CLI: 11.0.7
Node: 14.15.4
OS: darwin x64
Scully Version:
"@scullyio/init": "^1.1.1",
"@scullyio/ng-lib": "^1.0.0",
"@scullyio/scully": "^1.0.0",
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:10 (1 by maintainers)
Top Results From Across the Web
building schematics gives error in angular 10 - Stack Overflow
P.S. I'm using Angular-10 to create library. Thanks. ... At the root level package.json file, add this under scripts section - "alternate": "./ ......
Read more >How To Solve The Schematic Workflow Failed Error In Angular
Open VS Code, then go to the Terminal and click on the new terminal. Run the command “npm cache clean --force" which is...
Read more >Schematic "ng-new" not found in collection ... - GitHub
Update Angular CLI from version 1.7.6 to 6.0.1 using command "npm install -g @angular/cli"; Step 2 ... Generates an error: Schematic ...
Read more >yang-schematics - npm
The purpose of YANG is to create a more production-ready Angular application. It use the Angular Schematics to generate the code.
Read more >Collection "@igniteui/angular-schematics" cannot be resolved
Installed : C:\_ng\new_ig1>npm i -g @igniteui/angular-schematics. then run command below, and got the error, any advice why?
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I was able to make it work by changing the package.json as follow:
to
I have the same problem on a fresh angular project. This is the output I get: