Closed TatyanaMolchanova closed 1 year ago
Could you try to delete this line on serve-ssr: "defaultConfiguration": "development"
and "configuration.development
path. Then add options below builder like this:
"options": { "browserTarget": "client:build", "serverTarget": "client:server", },
I think the problem is that if you use a development configuration they try to use the same configuration on server and build, so if you don't have it have this problem.
We are wrongly assuming that users are using the @angular/cli
opt-in migration ng update @angular/cli --migrate-only production-by-default
to convert their projects to production by default, which will also create a development
configuration.
Note, in version 12, there is also a new experimental way of SSR, To opt-in you can use ng add @nguniversal/common
.
Could you try to delete this line on serve-ssr: "defaultConfiguration": "development" and "configuration.development path. Then add options below builder like this: "options": { "browserTarget": "client:build", "serverTarget": "client:server", },
Thank you, this helps. Now app is running. But for me as a newbie it is not obviously why after installing Angular 12 and Universal I can't run app by command from package.json.
Thank you for this bug fix. Now I will upgrade my new pet app to 12 Angular and will try TailWind with it.
Note, in version 12, there is also a new experimental way of SSR, To opt-in you can use
ng add @nguniversal/common
.
I created new Angular 12 app and install Universal with ng add @nguniversal/common
Then I tried to run app with npm run prerender
and got this error:
D:\PRACTICE\universal-angular12>npm run prerender
universal-angular12@0.0.0 prerender D:\PRACTICE\universal-angular12 ng run universal-angular12:prerender
An unhandled exception occurred: Could not find any routes to generate.
See "C:\Users\tanyamt\AppData\Local\Temp\ng-DOX2nI\angular-errors.log" for further details.
npm ERR! code ELIFECYCLE
npm ERR! syscall spawn
npm ERR! file C:\WINDOWS\system32\cmd.exe
npm ERR! errno ENOENT
npm ERR! universal-angular12@0.0.0 prerender: ng run universal-angular12:prerender
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the universal-angular12@0.0.0 prerender script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in: npm ERR! C:\Users\tanyamt\AppData\Roaming\npm-cache_logs\2021-06-19T15_54_57_513Z-debug.log
In log:
[error] Error: Could not find any routes to generate.
at D:\PRACTICE\universal-angular12\node_modules\@nguniversal\builders\src\static-generator\index.js:49:23
at Generator.next (
This command runs properly: npm run build:client-and-server
This command runs properly: npm run serve:ssr
Thank you for answer, but error in npm run prerender
will take me off using this experimental command in my real pet project.
@TatyanaMolchanova, ummm its strange that a no routes cannot be found when prerendering. Might sharing the project? Also, ideally this should be reported as a separate issue.
@TatyanaMolchanova, ummm its strange that a no routes cannot be found when prerendering. Might sharing the project? Also, ideally this should be reported as a separate issue.
I created new issue: https://github.com/angular/universal/issues/2179
This is the link to my repo with npm run prerender error: https://github.com/TatyanaMolchanova/angular12-universal-prerender-error
We are wrongly assuming that users are using the @angular/cli opt-in migration ng update @angular/cli --migrate-only production-by-default to convert their projects to production by default, which will also create a development configuration.
I ran into this issue as well. The above advise was tricky to follow, so here is my interpretation as a snippet..
angular.json
"serve-ssr": { "builder": "@nguniversal/builders:ssr-dev-server", "options": { "browserTarget": "app:build", "serverTarget": "app:server" }, "configurations": { "production": { "browserTarget": "app:build:production", "serverTarget": "app:server:production" } } },
Thanks for reporting this issue. This issue is now obsolete due to changes in the recent releases.
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.
I created new project - client - on Angular 11. Then updated ng version to 12 Angular. Then installed Universal: ng add @nguniversal/express-engine
Then I'm trying to run my Universal Angular, but it throws error:
npm run dev:ssr
client@0.0.0 dev:ssr ng run client:serve-ssr
This is a simple server for use in testing or debugging Angular applications locally. It hasn't been reviewed for security issues.
DON'T USE IT FOR PRODUCTION!
Configuration 'development' is not set in the workspace. npm ERR! code 1 npm ERR! path E:\PRACTICE\MYPETPROJECTS\tanechka\client npm ERR! command failed npm ERR! command C:\WINDOWS\system32\cmd.exe /d /s /c ng run client:serve-ssr
npm ERR! A complete log of this run can be found in: npm ERR! C:\Users\1\AppData\Local\npm-cache_logs\2021-06-08T14_35_07_681Z-debug.log
angular.json
`
package.json:
🐞 Bug report
What modules are related to this issue?
Is this a regression?
No, as I know, the previous version in which this bug was not present was. ### Description ## 🔬 Minimal Reproduction I tried to add 'development' to 'configurations' of serve: ``` `"serve": { "builder": "@angular-devkit/build-angular:dev-server", "options": { "browserTarget": "client:build" }, "configurations": { "production": { "browserTarget": "client:build:production" }, "development": { "browserTarget": "client:build:production" } } },` ``` But it didn't work. I tried to delete all node_modules and then install it, but it didn't work too. Please, help.