Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When using the Transloco service with Angular 11.1 getting ref error, works fine in 11.0.1 #19854

Closed
born2net opened this issue Jan 22, 2021 · 2 comments

Comments

@born2net
Copy link

I am not sure what other info I can provide as this is a large project.
but 100% if I switch back to 11.0.1 no issues and switching into the new 11.1 getting the following

using the popular package:
jsverse/transloco#396
works fine in 11.0.1 but with 11.1 getting:

Transloco

it is very odd is Transloco is loading fine with some modules and with others getting this error.
what other info can I provide?


Angular CLI: 11.1.0
Node: 10.15.0
OS: win32 x64

Angular: 11.1.0
... animations, cli, common, compiler, compiler-cli, core, forms
... language-service, localize, platform-browser
... platform-browser-dynamic, platform-server, router
... service-worker
Ivy Workspace: Yes

Package                            Version
------------------------------------------------------------
@angular-devkit/architect          0.1101.0
@angular-devkit/build-angular      0.1100.7
@angular-devkit/core               8.3.29
@angular-devkit/schematics         8.3.29
@angular/cdk                       11.0.0
@angular/flex-layout               10.0.0-beta.32
@angular/google-maps               9.2.4
@angular/http                      7.2.16
@angular/material                  11.0.0
@angular/material-moment-adapter   11.0.0
@angular/pwa                       0.803.29
@schematics/angular                8.3.29
@schematics/update                 0.1101.0
rxjs                               6.6.2
typescript                         4.0.5

thanks,

Sean.

@alan-agius4 alan-agius4 transferred this issue from angular/angular Jan 22, 2021
@alan-agius4
Copy link
Collaborator

Closing as a duplicate of #19839 and #19852, being fixed in #19841.

@angular-automatic-lock-bot
Copy link

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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Feb 22, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants