-
Notifications
You must be signed in to change notification settings - Fork 355
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 custom URL loaders #195
Comments
obviating the need for https://www.npmjs.com/package/resolve-url-loader which currently uses source maps to fix url()s that are relative to the source .scss module but not the compiled .css file. |
So, for node-sass users, I wrote eyeglass and one of it's main features is an entire solution around exposing assets for installation into an application from source locations in a npm module or application and assigning the right url to them according to application configuration. https://github.com/sass-eyeglass/eyeglass#working-with-assets Before Eyeglass, Compass provided this capability in ruby sass. I think this feature would be a good addition to Sass it would help standardize the implementation of asset helper tools and provide a consistent way for build pipeline integrations to address urls and imports in a holistic way and without forcing authors to opt in to a specific solution in order to interoperate. |
cc @xzyfer If we do this, we'd need to do it consistently across implementations. |
Agreed.
…On 21 Nov. 2017 12:10 pm, "Natalie Weizenbaum" ***@***.***> wrote:
cc @xzyfer <https://github.com/xzyfer>
If we do this, we'd need to do it consistently across implementations.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#195 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAjZWGS99C6wWlXdW4-SXPcFzJRoskv1ks5s4iLwgaJpZM4Qkggn>
.
|
Here's the libsass issue: sass/libsass#532
…On 21 Nov 2017 02:38, "Michael Mifsud" ***@***.***> wrote:
Agreed.
On 21 Nov. 2017 12:10 pm, "Natalie Weizenbaum" ***@***.***>
wrote:
> cc @xzyfer <https://github.com/xzyfer>
>
> If we do this, we'd need to do it consistently across implementations.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#195 (comment)>,
or mute
> the thread
> <https://github.com/notifications/unsubscribe-auth/AAjZWGS99C6wWlXdW4-
SXPcFzJRoskv1ks5s4iLwgaJpZM4Qkggn>
> .
>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#195 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAZQTKnvJH_KbOC-XlzyRt7fV9bjAhfoks5s4je2gaJpZM4Qkggn>
.
|
Discussion of the design for this loader should happen at sass/sass#2535. This issue will track the eventual implementation and the Dart API. |
similar to #9 but for:
The text was updated successfully, but these errors were encountered: