fix: handle css loader import option from

[RyanClementsHax]

fixes #19

Apparently the import option for css-loader gets passed arguments as specified on the v3 docs instead of v5 (which is the same as v4).

When I tried to use the v5 option structure, the webpack config validation errored with a link that import needed to be a boolean or a function, then linked me to this which clearly specifies that it should be the v5 option structure, not the v3 option structure.

What I had before is exactly how nextjs handles this, so I'm wondering if I'm missing a webpack config or something.

I'm at loss for how to get the seemingly proper solution, namely to make sure that the v5 option structure is used instead, or even to make it so this config can mirror what nextjs is doing.

This makes the basic fix to handle the case that it is passed an object or a string.

This also includes setting importLoaders to what nextjs sets its loaders to (1 for regular css, and 3 for sass) so the preprocessors can be called for imports. (Example)

[github-actions]

🎉 This PR is included in version 1.4.2 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀