Open razvanandreib opened 2 years ago
+1. I'm also running into same issue. It happens when I'm watching and make a syntax mistake. After rectifying it + save, the bundler does not automatically bundle. I had to close and re-watch. Strangely, I find that saving another file in your project somehow triggers the build. But working on the same file that had the mistake does not trigger anything.
This is probably a duplicate of #6685 or one of the 10+ linked issues from that ticket, like #5660.
Can someone post a reproduction with instructions on how to trigger this bug?
Sure. will come back with a screenshot.
Hey @mischnic,
It's my first time logging a bug, but I'll try to be concise:
Set up
index.html
inside the src folder.styles.scss
, I @import
another .scss file (let's call it header.scss
).Reproducing bug:
header.scss
, parcel encounters an error.I also discovered this set up works with normal .css files. It's Sass (maybe transformer-sass?) that is the problem.
I'm not sure if it's similar to what @razvanandreib is facing. If it's not, I can create a new issue.
I attached a screenshot with the bug. Immediately after I select an element in the scss file this error appear as in the screenshot u
I have exactly the same problem as @bensanlau.
The issue also occurs with pug files.
In my example: When I make a mistake in a file in "partials" directory, parcel encounters the error (like on @razvanandreib's screenshot) and I have to re-run the script or save not-imported/not-included* file (e.g. index.pug or bootstrap.scss).
*not-imported by @import
in scss and not-included by include
,extends
in pug.
My script: parcel pug/*.pug
@bensanlau Thanks! I can reproduce that.
This might also be happening for Elm: https://github.com/parcel-bundler/parcel/issues/6124
Actually, the problem seems to be that Sass, Elm and Pug all throw an error on a parser error and don't return the list of additionally included files (header.scss). So Parcel doesn't know that these other files also need to be watched.
Any updates here how to fix it? i don't want to relaunch dev every time i slowly typed {} 😁
Also experience this problem. Any updates?
Watching with interest for this bugfix. Thanks for the efforts fixing this!
🐛 bug report
As I start typing in the scss file , I immediately get this error and it happens everytime:
And parcel stops to function, i need to close it and npm start all over again.
🎛 Configuration (.babelrc, package.json, cli command)
🔦 Context
I try to write css in the scss files and immediatly after i start typing i get this error.
💻 Code Sample
🌍 Your Environment
| Node v17.1.0 | | npm/Yarn 8.1.2 | | Operating System Windows 10 |