Bug(scope): installation

[valeriorossi]

Is there an existing issue for this?

• [X] I have searched the existing issues

Which Transloco package(s) are the source of the bug?

Transloco

Is this a regression?

No

Current behavior

after package installation An unhandled exception occurred: Collection "C:\XY_Projects\tests\glob\globaliz\node_modules\@ngneat\transloco\schematics\src\collection.json" cannot be resolved.

Expected behavior

questions about languages, server, etc. as in the video tutorial

Please provide a link to a minimal reproduction of the bug

no link, just add transloco to a new angular app

Transloco Config

No response

Please provide the environment you discovered this bug in

Angular CLI: 12.2.17
Node: 14.18.0
Package Manager: npm 7.7.6
OS: win32 x64

Angular: 12.2.16
... animations, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1202.17
@angular-devkit/build-angular   12.2.17
@angular-devkit/core            12.2.17
@angular-devkit/schematics      12.2.17
@angular/cli                    12.2.17
@schematics/angular             12.2.17
rxjs                            6.6.7
typescript                      4.3.5

Browser

No response

Additional context

No response

I would like to make a pull request for this bug

No

[rgant]

Also experiencing this issue:

$ ng add @ngneat/transloco@3
ℹ Using package manager: npm
✔ Package information loaded.
 
The package @ngneat/transloco@3 will be installed and executed.
Would you like to proceed? Yes
✔ Package successfully installed.
An unhandled exception occurred: Collection "/Users/rgant/Programming/LearnLux/learnlux-app/node_modules/@ngneat/transloco/schematics/src/collection.json" cannot be resolved.
See "/private/var/folders/0z/3f6c6fvd75b9t93szh2_jjs00000gn/T/ng-sMbEt0/angular-errors.log" for further details.

$ ng version

     _                      _                 ____ _     ___
    / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
   / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
  / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
 /_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
                |___/
    

Angular CLI: 12.2.17
Node: 14.17.2
Package Manager: npm 6.14.13
OS: darwin x64

Angular: 12.2.16
... animations, common, compiler, compiler-cli, core, forms
... language-service, localize, platform-browser
... platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1202.17
@angular-devkit/build-angular   12.2.17
@angular-devkit/core            12.2.17
@angular-devkit/schematics      12.2.17
@angular/cli                    12.2.17
@angular/fire                   7.1.1
@schematics/angular             12.2.17
rxjs                            6.6.7
typescript                      4.3.5

$ git d package.json
────────────────────────────────────────────────────────────────────────────────────
modified: package.json
────────────────────────────────────────────────────────────────────────────────────
@@ -65,6 +65,7 @@
     "@firebase/app-types": "^0.7.0",
     "@formulajs/formulajs": "^3.0.0",
     "@ng-bootstrap/ng-bootstrap": "^10.0.0",
+    "@ngneat/transloco": "^3.2.0",
     "@sentry/angular": "^6.19.7",
     "@sentry/integrations": "^6.19.7",
     "@typeform/embed": "^1.35.1",

[rgant]

$ ng add @ngneat/[email protected]
ℹ Using package manager: npm
✔ Package information loaded.
 
The package @ngneat/[email protected] will be installed and executed.
Would you like to proceed? Yes
✔ Package successfully installed.
? 🌍 Which languages do you need? en, es
? 🚀 Are you working with server side rendering? No
Unexpected token / in JSON at position 1817

This error is because I have comments in my angular.json. Would be nice if this project used JSON5

[lightbyte]

Same issue here, and same configuration angular 12.2.16 and so. Installing [email protected] like @rgant said solved the problem because it has schemantics.

[shaharkazaz]

@rgant You are welcome to open a PR with this feature 👍 @lightbyte @valeriorossi A lot has passed since this issue, some published versions were missing the schematics due to build issues. I don't this is relevant anymore, if it is relevant, feel free to report it in a new issue.