Devon Govett

I think that's because when you delete a file, it only moves it to the trash. Then when you undo, it moves it back. So actually macOS delivers a rename...

> keep the invalid css to leave it processed by other tools Can you make pre-processors run before lightningcss so that the input to lightningcss is valid? Skipping over invalid...

> actually it's decided by users Could it be considered a configuration error though? That's like if the JS parser also had to accept coffeescript as input.

I think all of those examples already work [see here](https://lightningcss.dev/playground/index.html#%7B%22minify%22%3Afalse%2C%22customMedia%22%3Atrue%2C%22cssModules%22%3Afalse%2C%22analyzeDependencies%22%3Afalse%2C%22targets%22%3A%7B%22chrome%22%3A6225920%7D%2C%22include%22%3A0%2C%22exclude%22%3A0%2C%22source%22%3A%22%2F*%20deep%20selectors%20*%2F%5Cn%3A%3Av-deep(.foo)%20%7B%5Cn%20%20color%3A%20red%3B%5Cn%7D%5Cn%2F*%20shorthand%20*%2F%5Cn%3Adeep(.foo)%20%7B%5Cn%20%20color%3A%20red%3B%5Cn%7D%5Cn%5Cn%2F*%20targeting%20slot%20content%20*%2F%5Cn%3A%3Av-slotted(.foo)%20%7B%5Cn%20%20color%3A%20red%3B%5Cn%7D%5Cn%2F*%20shorthand%20*%2F%5Cn%3Aslotted(.foo)%20%7B%5Cn%20%20color%3A%20red%3B%5Cn%7D%5Cn%5Cn%2F*%20one-off%20global%20rule%20*%2F%5Cn%3A%3Av-global(.foo)%20%7B%5Cn%20%20color%3A%20red%3B%5Cn%7D%5Cn%2F*%20shorthand%20*%2F%5Cn%3Aglobal(.foo)%20%7B%5Cn%20%20color%3A%20red%3B%5Cn%7D%22%2C%22visitorEnabled%22%3Afalse%2C%22visitor%22%3A%22%7B%5Cn%20%20Color(color)%20%7B%5Cn%20%20%20%20if%20(color.type%20%3D%3D%3D%20'rgb')%20%7B%5Cn%20%20%20%20%20%20color.g%20%3D%200%3B%5Cn%20%20%20%20%20%20return%20color%3B%5Cn%20%20%20%20%7D%5Cn%20%20%7D%5Cn%7D%22%2C%22unusedSymbols%22%3A%5B%5D%2C%22version%22%3A%22local%22%7D), just with warnings. Do you have a list of cases that produce broken output/errors?

We may be able to publish the source files. The thing I'd be worried about and need to look into is whether including the `binding.gyp` causes npm to always build...

Do you watch overlapping folders? I was thinking at some point of automatically avoiding that in the watcher library itself but maybe for now you can do that yourself in...

Thanks for the deep investigation here! This looks good to me.

Parcel doesn't edit package.json, it just runs a package manager like yarn or npm, which may edit the package.json to add the dependency. Not sure what would be causing it...

Btw you can run with the `--no-autoinstall` flag to prevent automatic installation from being run, which might be a workaround while we figure this out.

Hmm strange. So I made a example project with these files: package.json: ```json { "name": "test", "scripts": { "build": "parcel build test.styl" }, "dependencies": { "parcel": "^2.0.1" } } ```...