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
[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report
[ ] Performance issue
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request
[ ] Other... Please describe:
Current behavior
After following the installation steps from the README.md, I started using @ngneat/svg-generator via npm script command"svg": "svg-generator". I faced the following error (attached screenshot) in the terminal.
After installing svgo as a devDependency, the issue has gone
Expected behavior
No issues during the process of using @ngneat/svg-generator. svgo installs within the package
Minimal reproduction of the problem with instructions
Generate a new Angular application. Run the following commands:
yarn add @ngneat/svg-icon
yarn add @ngneat/svg-generator -D
The previous commands added the following dependencies to the package.json
What is the motivation / use case for changing the behavior?
It will be great not to face the issue and get all the dependencies within the package (i.e. npm i | yarn add).
Environment
Angular version: 16.1.0
Browser:
- [ ] Chrome (desktop) version XX
- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX
For Tooling issues:
- Node version: 16.20.1
- Platform: Mac
Others:
- Package manager: yarn
- yarn version: 1.22.0
The text was updated successfully, but these errors were encountered:
I'm submitting a...
Current behavior
After following the installation steps from the README.md, I started using @ngneat/svg-generator via npm script command
"svg": "svg-generator"
. I faced the following error (attached screenshot) in the terminal.After installing svgo as a
devDependency
, the issue has goneExpected behavior
No issues during the process of using
@ngneat/svg-generator
. svgo installs within the packageMinimal reproduction of the problem with instructions
Generate a new Angular application. Run the following commands:
yarn add @ngneat/svg-icon
yarn add @ngneat/svg-generator -D
The previous commands added the following dependencies to the
package.json
What is the motivation / use case for changing the behavior?
It will be great not to face the issue and get all the dependencies within the package (i.e.
npm i | yarn add
).Environment
The text was updated successfully, but these errors were encountered: