GitShow/vuejs/vue-loader
vuejs

vue-loader

๐Ÿ“ฆ Webpack loader for Vue.js components

by vuejs
hot-reloadsingle-file-componentvuewebpack
Star on GitHubForknpm

TypeScript

5.0k stars912 forks24 contributorsQuiet ยท 1y agoSince 2014v17.3.1MIT

Meet the team

See all 24 on GitHub โ†’
yyx990803
yyx990803133 contributions
haoqunjiang
haoqunjiang95 contributions
h-a-n-a
h-a-n-a3 contributions
Jinjiang
Jinjiang3 contributions
danielroe
danielroe1 contribution
xanf
xanf1 contribution
Jamie-Yang
Jamie-Yang1 contribution
thecrypticace
thecrypticace1 contribution

Languages

View on GitHub โ†’
TypeScript91.4%
JavaScript6.7%
Vue1.9%
HTML0.1%

Commit activity

Last 12 weeks ยท 0 commits

Full graph โ†’

Community health

2 of 6 standards met

Community profile โ†’
37
โœ“READMEโœ“Licenseโ—‹Contributingโ—‹Code of Conductโ—‹Issue Templateโ—‹PR Template

Recent PRs & issues

Quiet ยท Last activity 1y ago
See all on GitHub โ†’
grigoryvp
Is it possible to make "scoped" components style leak optional?OpenIssue

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

grigoryvp ยท 3mo ago
axetroy
Remove `webpack` from runtime dependenciesOpenIssue

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)

axetroy ยท 4mo ago
sebastienroul
Tricky Src Imports : no compile or hot-reload with version 17.4.2OpenIssue

Using Webpack 3.12.4 + vue-loader 17.4.2. Our practice is to split html and js (for maintenance purpose) Here is a simplified sample of what we have index.vue index.html And then fail in compilation with 'Invalid end tag'.... Fix try We try to fix it, by encapsulating the html code in a template : TemplateloaderdescriptordescriptorCacheTemplateLoadercompileTemplateTemplateLoadercompilerast`, not with the modified source Then hot-reload happened, but not with the new code, only with original source ast-parsed. Sorry for being so long to explain, but it's tricky. Let me know if you need any explanation or info. Regards

sebastienroul ยท 7mo ago

Recent fixes

View closed PRs โ†’
fi3ework
fix: treat `with` as known loader rule propertyMergedPR

to supersede https://github.com/web-infra-dev/rsbuild/pull/6388.

fi3ework ยท 8mo ago
jh-thank-you
vue-loader not processing images in dynamic componentClosedIssue

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

jh-thank-you ยท 8mo ago
lucasmpaim
Unable to use a compiler proxyClosedIssue

Version 15.4.2 Reproduction link https://github.com/lucasmpaim/testbuild Steps to reproduce run yarn build What is expected? The build has compiled without problem What is actually happening? raised a error compiler.parseComponent is not a function Using this solution: https://github.com/vuejs/vue/issues/3934 with vue-cli project With this configuration: on build process I receive the exception: , In development is working perfectly, in I put an to check why this is happening, and I notice in sometimes the compiler is a blank object . The log: Adding: Before parser executes, everting work fine.

lucasmpaim ยท 9mo ago
Structured data for AI agents

Repository: vuejs/vue-loader. Description: ๐Ÿ“ฆ Webpack loader for Vue.js components Stars: 4967, Forks: 912. 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: 46, open issues: 186. Last activity: 1y ago. Community health: 37%. Top contributors: yyx990803, haoqunjiang, h-a-n-a, Jinjiang, danielroe, xanf, Jamie-Yang, thecrypticace, JuniorTour, merceyz and others.

ยท@ofershap

Replace github.com with gitshow.dev