-
Notifications
You must be signed in to change notification settings - Fork 32
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
Support svelte.preprocess #6
Comments
FYI I've opened a ticket — sveltejs/svelte#1101 — to discuss whether a svelte.config.js file is something that should be 'officially' supported rather than a Parcel-specific thing |
I'll implement this once the standardised config is in place |
@DorianGrey I implemented it, let me know what you think and if it works as expected 4c46de0 |
Looks good structurally. |
Here it is: Extremely simple, stripped down to a minimum to illustrate the |
Thanks so much for reviewing and setting up an example 👍 I'll push a new released to npm in a few secs |
Link to example is broken.. any resource to see how this works? |
The following worked for me. You need to install a svelte pre-processor plugin to process sass, I used the following plugin Add a file with the name
If you want to use it just add |
Hi there,
since V1.44.0,
svelte
supports a preprocessing step, e.g. to renderscss
if used. The API is documented here.Just an example of what this might look like resp. result in:
(extracted from the
svelte-loader
behavior)Supporting this would require to use an external config file that is not in JSON format, since preprocessing requires functions. Maybe something like a
.svelte.config.js
? It might be possible to put the generalsvelte
options there as well and only pick the current definition in case the file is absent.E.g. -
.svelte.config.js
:The text was updated successfully, but these errors were encountered: