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
Which @angular/* package(s) are the source of the bug?
@nguniversal/express-engine or @angular/ssr
Is this a regression?
No
Description
After the migration to Angular v17 (in an nx workspace) I am facing the error that the REQUEST InjectionToken cannot be found anymore. Since the @nguniversal/express-engine package got removed I can't find the InjectionToken in e.g. the @angular/ssr package.
Did you get any errors while running the migrations ? The schematics should handle that for you.
It creates a src/express.tokens.ts that contains the token definitions. Do you have it ? (See #26323 which is a closely related issue).
Nx implements the migrations themselves, and this particular one is present in Nx 17.1.
Since the tokens now have to be provided by user code and the CLI provides a migration to set this up, I am going to close this since Nx was used to update, not the CLI directly.
Which @angular/* package(s) are the source of the bug?
@nguniversal/express-engine or @angular/ssr
Is this a regression?
No
Description
After the migration to Angular v17 (in an nx workspace) I am facing the error that the
REQUEST
InjectionToken cannot be found anymore. Since the@nguniversal/express-engine
package got removed I can't find the InjectionToken in e.g. the @angular/ssr package.How can I access the request object as described here? https://www.npmjs.com/package/@nguniversal/express-engine#using-the-request-and-response
Please provide a link to a minimal reproduction of the bug
https://www.npmjs.com/package/@nguniversal/express-engine#using-the-request-and-response
Please provide the exception or error you saw
Please provide the environment you discovered this bug in (run
ng version
)Anything else?
I migrated to angular via the Nx workspace migration tool (
nx migrate latest
&npx nx migrate --run-migrations --create-commits
)The text was updated successfully, but these errors were encountered: