Last 12 weeks · 0 commits
2 of 6 standards met
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)
Repository: vuejs/vue-loader. Description: 📦 Webpack loader for Vue.js components Stars: 4979, Forks: 916. 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.
TypeScript
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
Version 16.0.0-beta.8 Reproduction link https://github.com/idrunk/vue-loader-bug-reproduction Steps to reproduce 配置webpack的cache.type为filesystem, 开启缓存 初始化一个Vue3 Typescript的项目, 建立一个根单文件组件并使用ts版setup语法糖, 建立一个子单文件组件并使用ts版setup语法糖, 在根组件中导入子组件 第一次编译, 正常通过能运行 (补充, 这里漏了关键一步, 就是这里需要改动inside.vue的模板内容, 即让缓存失效, 然后再编译才会失败, 否则直接用缓存的话则不会失败) 后续编译, 编译失败, 报下述错误 What is expected? 编译通过 What is actually happening? 编译失败 经过跟踪排查, 发现在前行(index.js:58)插入下述代码, 多次编译都能正常通过, 但我感觉这不是解决之道
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
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.