-
Notifications
You must be signed in to change notification settings - Fork 12k
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
Build application with prerender routes file fails #27251
Comments
This seems like a bug but we'll need to look at a reproduction to find and fix the problem. Can you setup a minimal repro please? You can read here why this is needed. A good way to make a minimal repro is to create a new app via This might be related to your directory structure so its really important to get an accurate repro to diagnose this. |
Hi, Sure: https://github.com/WhizUs-Labs/angular-prerender-test My serve is also not working with this example. Maybe it is just a config issue, but what definitely is a bug is the error message, because object object doesn´t help to solve the issue.
|
The problem in this case is that the "server" entrypoint is not defined. I'll open a PR to fix the error message. |
… server option is required but missing This improves the error message when the server entry-point is required but missing Closes angular#27251
… server option is required but missing This improves the error message when the server entry-point is required but missing Closes angular#27251
…inating in ESM loader hooks Currently, errors occurring in ESM loader hooks while using `--import` are not correctly displayed, as they cannot be transferred from the worker to the main thread. Although the error is an instance of Error, it contains non-transferable properties and cannot be transmitted from a worker when --import is used. Consequently, when read outside of the worker, the error object displays as `[Object object]`. To address this issue, we reconstruct the error message. See: angular#27251
…inating in ESM loader hooks Currently, errors occurring in ESM loader hooks while using `--import` are not correctly displayed, as they cannot be transferred from the worker to the main thread. Although the error is an instance of Error, it contains non-transferable properties and cannot be transmitted from a worker when --import is used. Consequently, when read outside of the worker, the error object displays as `[Object object]`. To address this issue, we reconstruct the error message. See: angular#27251
…inating in ESM loader hooks Currently, errors occurring in ESM loader hooks while using `--import` are not correctly displayed, as they cannot be transferred from the worker to the main thread. Although the error is an instance of Error, it contains non-transferable properties and cannot be transmitted from a worker when --import is used. Consequently, when read outside of the worker, the error object displays as `[Object object]`. To address this issue, we reconstruct the error message. See: angular#27251
… server option is required but missing This improves the error message when the server entry-point is required but missing Closes #27251
…inating in ESM loader hooks Currently, errors occurring in ESM loader hooks while using `--import` are not correctly displayed, as they cannot be transferred from the worker to the main thread. Although the error is an instance of Error, it contains non-transferable properties and cannot be transmitted from a worker when --import is used. Consequently, when read outside of the worker, the error object displays as `[Object object]`. To address this issue, we reconstruct the error message. See: #27251
…inating in ESM loader hooks Currently, errors occurring in ESM loader hooks while using `--import` are not correctly displayed, as they cannot be transferred from the worker to the main thread. Although the error is an instance of Error, it contains non-transferable properties and cannot be transmitted from a worker when --import is used. Consequently, when read outside of the worker, the error object displays as `[Object object]`. To address this issue, we reconstruct the error message. See: #27251 (cherry picked from commit 51debcd)
…inating in ESM loader hooks Currently, errors occurring in ESM loader hooks while using `--import` are not correctly displayed, as they cannot be transferred from the worker to the main thread. Although the error is an instance of Error, it contains non-transferable properties and cannot be transmitted from a worker when --import is used. Consequently, when read outside of the worker, the error object displays as `[Object object]`. To address this issue, we reconstruct the error message. See: #27251 (cherry picked from commit 51debcd)
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Which @angular/* package(s) are the source of the bug?
compiler
Is this a regression?
Yes
Description
I migrated my app to Angular 17 --> works as expected.
Now I want to get rid of my webpack build.
So I migrate my prerendering to @angular-devkit/build-angular:application:
when I run then the build with ng build I get following error:
This only happens when prerender options is:
my routes.txt is correct.
Please provide a link to a minimal reproduction of the bug
https://github.com/WhizUs-Labs/angular-prerender-test
Please provide the exception or error you saw
Please provide the environment you discovered this bug in (run
ng version
)Anything else?
No response
The text was updated successfully, but these errors were encountered: