Error creating application with @angular/bazel
See original GitHub issue🐞 Bug report
I would like to try Angular with Bazel following the instructions of the page https://next.angular.io/guide/bazel but I have errors both during the ng new and during the ng build
Command (mark with an x
)
- [x] new
- [x] build
Description
ng new --collection=@angular/bazel
throws an error
EDIT: After installing @angular/bazel package, also ng build throws an ERROR
🔬 Minimal Reproduction
npm i -g @angular/cli@next @angular/bazel@next
ng new --collection=@angular/bazel
🔥 Exception or Error
An unhandled exception occurred: Cannot find module '@angular-devkit/schematics'
Require stack:
- C:\Users\Admin\AppData\Roaming\npm\node_modules\@angular\bazel\src\schematics\ng-new\index.js
- C:\Users\Admin\AppData\Roaming\npm\node_modules\@angular\cli\node_modules\@angular-devkit\schematics\tools\export-ref.js
- C:\Users\Admin\AppData\Roaming\npm\node_modules\@angular\cli\node_modules\@angular-devkit\schematics\tools\index.js
- C:\Users\Admin\AppData\Roaming\npm\node_modules\@angular\cli\utilities\json-schema.js
- C:\Users\Admin\AppData\Roaming\npm\node_modules\@angular\cli\models\command-runner.js
- C:\Users\Admin\AppData\Roaming\npm\node_modules\@angular\cli\lib\cli\index.js
- C:\Users\Admin\AppData\Roaming\npm\node_modules\@angular\cli\lib\init.js
- C:\Users\Admin\AppData\Roaming\npm\node_modules\@angular\cli\bin\ng
See "C:\Users\Admin\AppData\Local\Temp\ng-2XKNxH\angular-errors.log" for further details.
🌍 Your Environment
Angular CLI: 9.0.0-rc.1
Node: 12.13.0
OS: win32 x64
Angular:
...
Package Version
------------------------------------------------------
@angular-devkit/architect 0.900.0-rc.1
@angular-devkit/core 9.0.0-rc.1
@angular-devkit/schematics 9.0.0-rc.1
@schematics/angular 9.0.0-rc.1
@schematics/update 0.900.0-rc.1
rxjs 6.5.3
Anything else relevant? I tried to do
ng new bazel-project
# and
ng add @angular/bazel
but with this output:
Installing packages for tooling via npm.
An unhandled exception occurred: spawnSync npm ENOENT
Package install failed, see above.
See "C:\Users\Admin\AppData\Local\Temp\ng-j3oYip\angular-errors.log" for further details.
EDIT: `ng add @angular/bazel’ throws an error but will be solved with angular/angular-cli#16112
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:12 (6 by maintainers)
Top Results From Across the Web
Why does Angular CLI 9.01 fails to create a bazel project?
I erease Node and Angular from my machine, and re-installed them from scratch. The, I followed these instructions to create a new ng...
Read more >Build your Angular application with Bazel | Ninja Squad
Trying to create a Bazel project as described currently fails with error: (node_modules/@angular/router/upgrade/src/upgrade.d.ts(9,31): error ...
Read more >Angular 8 - Bazel Walkthrough - Bits and Pieces - Bit.dev
Ever seen this error when trying to build your application using Bazel? UMD and IIFE output formats are not supported for code-splitting builds....
Read more >Examples | rules_nodejs - GitHub Pages
Angular. Bazel can run any toolchain you want, so there is more than one way to ... create-react-app: If you run create-react-app ,...
Read more >Angular compiler options
Used by the Bazel build rules to simplify how Bazel rules track file ... Instructs the Angular template compiler to create legacy ids...
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 Free
Top 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
The second issue is the same as https://github.com/angular/angular-cli/issues/16115 and will be solved with https://github.com/angular/angular-cli/pull/16112
This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.