-
Notifications
You must be signed in to change notification settings - Fork 2
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
🐛 On Angular-Cli projects built with "ng new Demo_Project --style=scss" parcel can't compile scss #3
Comments
I cloned the repo you linked in the other issue on {
"compilerOptions": { /* your options*/ },
"include": [
"src/**/*.ts"
]
} You can also check if node-sass is correctly installed : run |
in that shared repo the package.json (and the project) is still set up to use (you also need to un-comment two lines in html.index) I added your fix (I'd forgotten about that file, with all the things I keep changing in the setup, sorry about that), and I did
|
wtf??? how come your scss compiles? this is crazy. I added you as collaborator so you can push there. (careful i removed all the backend, try re-cloning) thanks for continuing to help my noob self 🙁 |
i'm pretty sure it comes from Windows, i'll push this to your repo once I get home and check that :) |
ok. I cleaned up the repo and brought it up to speed. |
did you figure it out? if the new updates to the repo are of a breaking sort could you push whatever worked to another branch? |
Ok.. so weird. can you push what you have to my repo? even though I also use chrome I only noticed such a discoloration towards bright cyan for the "goo" parts on firefox, for chrome, it's supposed to look like this : and like you had previously : #3 (comment) also notice how the html and body margin and padding 0 are ignored. But I'm nitpicking I'd much rather have this state than continue sticking with ng serve/build |
is it possible it's because the I turned root css file into an scss file? on my "ng serve project", reverting that allowed me to have working browsing transitions (still with scss on the rest of the project) Maybe having a root scss file is not allowed. just like having an html file as root is mandatory. the difference being that a root scss file doesn't completely crash the project. |
🎛 Configuration (.babelrc, package.json, cli command)
🤔 Expected Behavior
scss is compiled on both
ng serve
andparcel ./src/index.html
😯 Current Behavior
ng serve
creates project with compiled scss.parcel ./src/index.html
ignores scss files entirely and outputs this error :💁 Possible Solution
path into angular-cli's usage of scss compilation and use it for parcel or make sure parcel continues to use node-sass as it does with React.
💻 Code Sample
ts.config.json :
index.html :
🌍 Your Environment
also my stack shows this bug : PatrickJS/PatrickJS-starter#1555 : if any scss files that are present are empty the rather than serving the app without loading any style (as I have right now) it fails to compile at all. with :
Unhandled promise rejection: Error: Error: Error: Could not find file: 'C:\Users\j_bard\WebstormProjects\AirConnect\web\web.ui\src\polyfills.ts'.
The text was updated successfully, but these errors were encountered: