"Uncaught Error: Element type is invalid" if .scss file with same base name exists in importing file's folder about meteor-scss HOT 2 OPEN

This isn't really a bug. It doesn't know whether you want to import App.jsx or App.scss since both can be imported. With this package you are allowed to do (for example in your App.jsx):

import {App as Something} from './App.scss';

from meteor-scss.

Hi! I'm facing the same issue. It's not really a bug but very inconvenient...
In my case, I'm in the process of removing Webpack from a project with ~1000 of files containing several import statements that don't specify the file extension. Actually, only the .scss extensions are specified when needed.
Is there a way to establish a priority order?
If so, IMHO it would make sense that the default case when no extension is present should be to try to load a .jsx file.
What do you think?

from meteor-scss.