-
Notifications
You must be signed in to change notification settings - Fork 7
Not compatible with normal postcss-import
URL references
#9
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
Comments
hi Mike! I'm one of maintainers of this plugin. Thank you for raising this, I think we have enough info to start working. I'll keep you updated. If all goes well, if I can make it work on my local, I'll need your help to test it out. |
I might also be available to test. I ran into this blocker (after I begrudgingly updated my import path to move past #7). Reminder to Self@wesleyboar, you had tested this plugin as a replacement for https://github.com/travco/postcss-extend, but this bug may have stopped you from continuing, but you don't see |
hi all, try v1 that has been just released, we renamed the handle to |
Fixed #11 |
Is this issue closed with that fix? |
We have this in our css file from when using the normal
postcss-import
plugin:@import url('https://rsms.me/inter/inter.css');
When adding
postcss-nested-import
now we get an error on this line. Is there a way to usepostcss-nested-import
along with thepostcss-import
so we can have the nested import in selectors but not break the top-level imports that were working?Maybe it would be better to change the "node" name being used in the plugin from the default
import
to something unique likeimport-nested
so this plugin could be used only for the nested import and not worried about replicating the functionality ofpostcss-import
?The text was updated successfully, but these errors were encountered: