Comments (3)
Why do you think having a query parameter is better than using generateScopedName
?
from vite.
Why do you think having a query parameter is better than using
generateScopedName
?
a query parameter allows you to handle complex situation, while generateScopedName
is a static rule based on filepath etc. For example
// full path is src/order/product/index.module.css
import styles from './index.module.css?prefix=OrderProduct';
// full path is src/order/product/Cover.module.css
import styles from './Cover.module.css?prefix=OrderProductStatus';
Both query parameter and generateScopedName
have their advantages.
from vite.
while
generateScopedName
is a static rule based on filepath etc.
You can use pass a function to generateScopedName
.
generateScopedName: function (name, filename, css) {
const map = { 'src/order/product/index.module.css': 'OrderProduct' }
const mapped = map[normalize(filename)]
const line = css.substr(0, i).split(/[\r\n]/).length;
const file = path.basename(filename, ".css");
return "_" + map + "_" + line + "_" + name;
},
I noticed now that importing a same file with different query would be a problem.
// src/foo.js
import styles from './index.module.css?prefix=OrderProduct';
// src/bar.js
import styles from './index.module.css?prefix=OrderProductStatus';
from vite.
Related Issues (20)
- vite can not get cookie from set-cookie HOT 3
- Allow plugins to hook into `preprocessCSS()` HOT 9
- Got wrong url when importing some svg files HOT 5
- The object is created with the old class name, but the instanceof check is performed with the renamed class name HOT 1
- Unable to exclude certain css `@import` statements from getting inlined HOT 3
- 5.4.3 production bug HOT 2
- Improper escaping of HTML attribute when `transformIndexHtml` is used HOT 1
- failed CSS preloads prevent loading dependencies HOT 1
- [vite:css] [postcss] ENOENT: no such file or directory
- Issues with dynamic import of static JS file HOT 2
- Modifications to the `server.proxy` in the plugin API `configureServer` did not take effect HOT 1
- Testing files are not excluded on prod build HOT 2
- `fetchpriority` attribute in `<script>` is stripped from `index.html` after build HOT 2
- An option to inject CSS styles into the generated .html files <head> tag instead of separate .css files
- When importing wrong local files shows no error. HOT 4
- Expose dev, preview URLs as env variables. HOT 1
- Share chunks between multiple ESM Workers HOT 1
- Create Vite - Remix - "remix command not found" HOT 3
- Not detected recurrence in scss code (@mixin calling itself) leading to build failure HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from vite.