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
Hi. we are encountering an issue , when we build the project using npm run build we face a problem with css ordering at the end . in the project we have a style.css file which has to override all the styles at the end . it works fine in the development mode. but when we build the project using npm run build command , what we see is that some node_module dependency styles are being placed after our style.css styles. how can we prevent that? how can we make sure that our style.css style codes ALWAYS comes last in the process of building our project?
any help will be much appreciated . i know it might not be a boilerplate Direct issue but still , we are facing this problem . thanks in advance .
The text was updated successfully, but these errors were encountered:
Ok , a friend of mine solved this problem for us , for anyone who is facing a similar problem, you need to require your styles in app.init.js file . and if u have anything addresses with url() in your css files you need to put a ~ before your address . like this :
background: url('~/src/assets/imgs/homeBackground.png');
Hi. we are encountering an issue , when we build the project using npm run build we face a problem with css ordering at the end . in the project we have a style.css file which has to override all the styles at the end . it works fine in the development mode. but when we build the project using npm run build command , what we see is that some node_module dependency styles are being placed after our style.css styles. how can we prevent that? how can we make sure that our style.css style codes ALWAYS comes last in the process of building our project?
any help will be much appreciated . i know it might not be a boilerplate Direct issue but still , we are facing this problem . thanks in advance .
The text was updated successfully, but these errors were encountered: