feat: Fall back to `.css` files if no `.scss` file found
In #48, it was noted that all import paths had the .scss extension added if not already present. A fix was merged which solved the situation of a .css extension being specified, but it did not solve the case where an import is for a .css file but does not specify the extension. This change solves that by falling back to looking for .css files if a .scss file cannot be found.
We are bundling some SCSS which relies on libraries that use CSS files and don't include SCSS. This change would be very useful.
This feels like a sensible enough default, though it may be preferable to put this behavior behind a configuration option.
@DovydasNavickas @MartynasZilinskas Is this project still maintained? Would be great to get this small change merged and released.
Hi @gbannerman,
The project is not much maintained as it needs a bigger rewrite to support new SCSS features, but PRs like yours can be merged.
That said, I would rather you added the functionality behind a flag or we release it under a major version. This might break someone's project and as the library has a long history and I wouldn't want to break very old projects.
I would rather you added the functionality behind a flag or we release it under a major version
Yes I agree that's a safer approach. I can update this PR to use a flag.