You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When trying to generate a spectator-component with the angular cli ng generate @ngneat/spectator:spectator-component you receive the following error: '[project folder]/node_modules/@ngneat/spectator/schematics/collection.json cannot be resolved.'
When you take a look inside your node_modules/@ngneat/spectator folder the schematics folder is indeed missing.
It seems that the schematics folder is missing from the npm package since version 11.0.0.
If you install version 10.0.1 the ng generate is working again so this was working before and the schematics folder is present.
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
An unhandled exception occurred: Collection "[project folder]/node_modules/@ngneat/spectator/schematics/collection.json" cannot be resolved.
Please provide the environment you discovered this bug in
No response
Anything else?
No response
Do you want to create a pull request?
No
The text was updated successfully, but these errors were encountered:
Is this a regression?
Yes
Description
When trying to generate a spectator-component with the angular cli
ng generate @ngneat/spectator:spectator-component
you receive the following error: '[project folder]/node_modules/@ngneat/spectator/schematics/collection.json
cannot be resolved.'When you take a look inside your
node_modules/@ngneat/spectator
folder the schematics folder is indeed missing.It seems that the schematics folder is missing from the npm package since version 11.0.0.
If you install version 10.0.1 the
ng generate
is working again so this was working before and the schematics folder is present.Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
Please provide the environment you discovered this bug in
No response
Anything else?
No response
Do you want to create a pull request?
No
The text was updated successfully, but these errors were encountered: