Commit activity
Last 12 weeks · 0 commits
Community health
2 of 6 standards met
37
✓README✓License○Contributing○Code of Conduct○Issue Template○PR Template
Recent PRs & issues
Quiet · Last activity 2y ago
See all on GitHub →
What problem does this feature solve? Disclaimer: I could not create this issue via the Vue.js issue helper and therefore unfortunately could not auto-attach the label. Got a error from the GitHub servers, apparently this proposal is just too long to fit into a URL. 🙃 For Clarification: Whenever this proposal mentions parent/child components, it's not about nesting (as in / ) but about the relation between two components where one the other. Status Quo As described in this forum thread, there currently seems to be a lack of an easy way to incrementally add scoped styles to child components. This makes creating reusable components harder than it needs to be. Regarding styles, using currently is an all-or-nothing approach: When *no `data-v-data-v-extendsScopedStylefalseextendextendsScopedStyletruedata-v-data-v-ABBCdata-v-CBAnameextends-scoped-styleextends-scoped-style` blocks in the same component — some may have that marker attribute, others may not. This would be a weird inconsistency because the feature can only be an on/off thing for the component as a whole.
What problem does this feature solve? Right now "scoped" is not really scope: styles from components leak to child components (this is by design, "A child component's root node will be affected by both the parent's scoped CSS and the child's scoped CSS."). Is it possible to make such feature optional? In practice, I often define simple class names like "root" for flex-placing children and it always leak to child components, wreaking hawok to ones that are unfortunate enough to use same short names. Right now the workaround is to use "module" syntax, but it adds lots of unneded text, especially if compilers like PUG are used for CSS. Making vuejs config option like "dontLeakScopedModules" with default to "false" will be a bless! I can create a patch, if it's an acceptable feature and i'm not getting anything of this wrong. What does the proposed API look like? { test: /\.vue$/, loader: 'vue-loader', options: { dontLeakScopedModules: true
https://github.com/search?q=repo%3Avuejs%2Fvue-loader%20require(%27webpack&type=code I found that the plugin has a runtime dependency on webpack. As rspack matures, this is a barrier to migration. We should remove the runtime dependency on webpack We can get the webpack's Plugin via compiler instead of , which is compatible with webpack-like bundler(eg. rspack)
Recent fixes
This will allow to populate manually predefined global var "VUE_SSR_CONTEXT" on server side rendering in php/v8js
to supersede https://github.com/web-infra-dev/rsbuild/pull/6388.
Vue Team, Thanks for all that you do for the dev community. I'm not sure if this is an issue or a configuration problem.** One of the contributors to webpack has been helping me sort an issue but we are at a point where he thinks it may be a vue-loader issue. I have a dynamic component/slot that is called via the data captured and passed by an Event Bus. This all work great and in development mode everything works as expected. When I build out the production folder the dynamic .vue template files are processed and placed in the correct directory (in the assets/modals folder) but none of the hard/static coded src links or src images in the template files are processed (no image hash and link hash updates are applied). I have a setup on github that's working via a hack (I am using Copy Webpack Plugin to copy over all the files in the directory) but this is just a quick fix for the above outlined issue. Here is the github repository: https://github.com/jh-thank-you/webpack-w-gsap Thanks again. All the best, Jim
Structured data for AI agents
Repository: vuejs/vue-loader. Description: 📦 Webpack loader for Vue.js components Stars: 4962, Forks: 908. Primary language: TypeScript. Languages: TypeScript (91.4%), JavaScript (6.7%), Vue (1.9%), HTML (0.1%). License: MIT. Topics: hot-reload, single-file-component, vue, webpack. Latest release: v17.3.1 (2y ago). Open PRs: 45, open issues: 186. Last activity: 2y ago. Community health: 37%. Top contributors: yyx990803, haoqunjiang, h-a-n-a, Jinjiang, danielroe, xanf, Jamie-Yang, thecrypticace, JuniorTour, merceyz and others.