Skip to content

Ignore url and @import #102

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

Closed
arb opened this issue Jul 14, 2015 · 6 comments
Closed

Ignore url and @import #102

arb opened this issue Jul 14, 2015 · 6 comments

Comments

@arb
Copy link

arb commented Jul 14, 2015

Provide a mechanism to ignore url and @import.

From GItter

arb can i use the CSS loader and make it ignore any @import or url()?
sokra 12:59
nope... but feel free to send a PR: css-loader?-url&-import

@RinatMullayanov
Copy link

+1 useful options

ShyykoSerhiy added a commit to ShyykoSerhiy/css-loader that referenced this issue Nov 13, 2015
@Phoenixmatrix
Copy link

A note of interest is that the older versions (eg: 0.14.5) DID have that feature: css?url=false

@download13
Copy link

I could use this feature as well.

@djyde
Copy link

djyde commented Dec 7, 2015

+1.

For example:

@font-face {
  font-family: 'WhiteAdobeAndroid';
  src: url('file:///android_asset/fonts/AGaramondPro-Regular.otf') format('truetype'); 
}

I used a file url file:///android_asset, which only exists under Android platform. But css-loader would require ./file:///android_asset folder. I have no idea how to compile it to a normal text instead of using require.

But I didn't mean that I need an option for switching require or not require all urls. Instead, I need a way that I could tell the css-loader which path I don't want to be loaded.

@sokra sokra closed this as completed in 7b1e6f1 Dec 22, 2015
@djyde
Copy link

djyde commented Dec 25, 2015

Is there any way to disable the require behavior of a single place url() instead of disabling all files'?

@jrmyio
Copy link

jrmyio commented Jan 13, 2016

Also looking for a way to disable a siingle url() call. Currently CSS-Loader is kind of an all-or-nothing approach if I am correct? This makes it hard to upgrade legacy apps.

Edit: Just realized path that start with a / are excluded /images/test. However, I've been using ../images/ in all apps which does gets parsed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants