Skip to content
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

Watch stops on SCSS error #9060

Closed
tomootes opened this issue Jun 1, 2023 · 2 comments
Closed

Watch stops on SCSS error #9060

tomootes opened this issue Jun 1, 2023 · 2 comments

Comments

@tomootes
Copy link

tomootes commented Jun 1, 2023

🐛 bug report

When i'm using parcel watch without a configuration, the transpiler stops functioning when a SCSS error has occured. This means i'll have to restart the watch process and this distracts me from development work.

🎛 Configuration (.babelrc, package.json, cli command)

No configuration set. The watch process is called right away from the package.json.

🤔 Expected Behavior

I would expect the process to transpile again as soon as a change has been made to a .scss file.

😯 Current Behavior

The steps that i follow are:

  1. I run: parcel watch. The process starts to run: ✨ Built in 980ms.
  2. I make a change in a SCSS file which creates an error:
    Screenshot from 2023-05-31 09-28-11
  3. When i change the .scss file to resolve the error nothing happens. The transpiler doesn't run anymore and i have to restart the process.

💁 Possible Solution

Prevent the process from terminating when SCSS error occurs.

💻 Code Sample

Repo in which this occurs: https://gitlab.com/commonground/don/developer.overheid.nl

🌍 Your Environment

Software Version(s)
Parcel 2.9.1
Node v18.12.1
Yarn 3.5.1
Operating System Ubuntu 20.04.6 LTS
@mischnic
Copy link
Member

mischnic commented Jun 2, 2023

There's unfortunately nothing that Parcel can do here for now: #7374 (comment)

@mischnic mischnic closed this as not planned Won't fix, can't repro, duplicate, stale Jun 2, 2023
@tomootes
Copy link
Author

tomootes commented Jun 5, 2023

Alright. Thanks for the insight!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants