Closed Paul75 closed 2 years ago
Same thing! I have this error when trying to generate new project with
ngx new
Yarn seems to cause many errors lately with packages incorrectly installed, causing issues like this one.
You should be able to bypass this one by adding the flag --no-insights, but if generator-ngx-rocket is installed with npm and not yarn, this issues doesn't seems to occur at all.
I'm using npm, and just trying ngx new with some flag, and error disapear!
Running
ngx new --no-insights --no-analytics
, error is gone...
:tada: This issue has been resolved in version 10.1.2 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
I'm submitting a...
Current behavior
ngx update get errors :
ngx update
(node:3443) UnhandledPromiseRejectionWarning: TypeError: Use (/usr/local/lib/node_modules/generator-ngx-rocket/node_modules/yeoman-generator/lib/index.js:1024:25)
at /usr/local/lib/node_modules/generator-ngx-rocket/node_modules/run-async/index.js:49:25
at new Promise ()
at /usr/local/lib/node_modules/generator-ngx-rocket/node_modules/run-async/index.js:26:19
at runLoop.add.once.once (/usr/local/lib/node_modules/generator-ngx-rocket/node_modules/yeoman-generator/lib/index.js:1025:11)
at Immediate. (/usr/local/lib/node_modules/generator-ngx-rocket/node_modules/grouped-queue/lib/subqueue.js:48:34)
at processImmediate (internal/timers.js:464:21)
(Use
delete()
to clear values at Conf.set (/usr/local/lib/node_modules/generator-ngx-rocket/node_modules/conf/dist/source/index.js:165:19) at Insight.set optOut [as optOut] (/usr/local/lib/node_modules/generator-ngx-rocket/node_modules/insight/lib/index.js:56:15) at Object.initializing (/usr/local/lib/node_modules/generator-ngx-rocket/generators/app/index.js:57:25) at Object.node --trace-warnings ...
to show where the warning was created) (node:3443) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag--unhandled-rejections=strict
(see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2) (node:3443) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.Expected behavior
ngx update get errors
Minimal reproduction of the problem with instructions
do : ngx update
Environment
Others: