abp
abp copied to clipboard
can't run abp.io 6.0.0-rc.1 with Angular 14
GitHub Issues
can't run preview 6.0.0-rc.1 with angular
- Exception message and stack trace if available (check the logs).
./node_modules/@abp/ng.theme.lepton-x/assets/css/abp-bundle.css:1:0 - Error: Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> .confirmation .confirmation-backdrop {
| background: rgba(104, 107, 110, 0.5);
| }
./node_modules/@volo/ngx-lepton-x.lite/assets/css/bootstrap-dim.css:1:0 - Error: Module parse failed: Unexpected character '@' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> @charset "UTF-8";
| :root {
| --bs-blue: #0d6efd;
./node_modules/@volo/ngx-lepton-x.lite/assets/css/ng-bundle.css:1:0 - Error: Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> .node-wrapper {
| border-radius: 0.5rem;
| }
./node_modules/@volo/ngx-lepton-x.lite/assets/css/side-menu/layout-bundle.css:1:0 - Error: Module parse failed: Unexpected character '@' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> @import url("https://fonts.googleapis.com/css2?family=Inter:wght@100;200;300;400;500;600;700;800;900&display=swap");
| :root {
| --lpx-brand: #f72585;
- Steps needed to reproduce the problem.
- create a new startup template with angular
- update to angular 14
- run
In case some one need angular 14 right now with the preview, a workaround is to use basic theme:
- abp new AppName -u angular --preview --theme basic
- yarn add @abp/ng.theme.basic@~6.0.0-rc.1
Hello,
We will fix this error in lepton-x next version also we will update our templates angular version to 14
thanks @muhammedaltug
Is there a workaround for this issue? It appears it's not been resolved
Is there a workaround for this issue? It appears it's not been resolved
Create a new issue explaining the version you are using and re-production steps please.