How can i keep import path not parsed?
See original GitHub issuePrecheck
- Do a quick search and make sure a bug has not yet been reported;
- do a quick check if the bug still exists in the latest patch version;
- finally, be nice and have fun!
Environment
- clean-css version -
npm ls clean-css
: - node.js version -
node -v
: - operating system:
Configuration options
var CleanCSS = require('clean-css');
new CleanCSS({inline:false
})
Input CSS
/* the shorter the better! */
@import "../cell-group/index.wxss";
Actual output CSS
@import url(../cell-group/index.wxss);
Expected output CSS
@import "../cell-group/index.wxss";
How can I get it ?
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:6
Top Results From Across the Web
Absolute path import "from path import *" working but not ...
I just started working on a project where the import structure is something I have never seen. Here is the structure of the...
Read more >Absolute Path Imports not working · Issue #1734 - GitHub
import thing from 'src/app/path/to/thing';. Both my linter and ng build tell me that the module isn't found. What am I doing wrong? I...
Read more >How to Write Go Code - The Go Programming Language
Each module's path not only serves as an import path prefix for its packages, but also indicates where the go command should look...
Read more >CDKTF tsconfig paths not working for local imports
For a cleaner approach I am trying to not use relative path in my Typescript project like this. import { MyModel } from...
Read more >Documentation - Module Resolution - TypeScript
A non-relative import can be resolved relative to baseUrl , or through path mapping, which we'll cover below. They can also resolve to...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@yiqianglin and others - you are right, the shorter the better, so we should stick to the version without
url()
.However the issue says “How can I keep path not parsed?” - does it mean you want a way to keep it always as is? E.g. if there’s an import:
should we keep it as is or make it shorter?
I’m trying to understand requirements here.
Won’t fix as clean-css is going into maintenance mode.