vuejs-templates/webpack

[Placeholder]: Clear up situation with assets paths in production for css-loader

Open

#1,021 创建于 2017年11月1日

在 GitHub 查看
 (6 评论) (3 反应) (0 负责人)JavaScript (9,721 star) (4,466 fork)batch import
enhancementhelp wanted

描述

We have had multiple issues like #208 (#563, #552 ) which seem to show that under specific circumstances the paths generated by url-loader/file-loader are wrong.

But to be perfectly honest, I wasn't able to wrap my head around it, especially when trying to thing about how to test the proposed solution of using relative paths under various circumstances:

  • requiring assets in JS vs.in CSS
  • working paths when using vue-router in 'history' mode
  • working paths when using code-splitting

So If anyone can help shed some light on this and work out a robust solution, I'd be delighted.

贡献者指南

技术栈
javascriptnodejscss
领域
build systemfrontend
议题类型
research
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
4
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
over 1 week
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
needs investigation
前置要求
knowledge of webpack loadersunderstanding of CSS and JS asset pathsfamiliarity with vue router history modeexperience with code splitting
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
15
研究方向
The issue asks to investigate and resolve asset path problems in production with css loader. Focus on the proposed solution in comment https://github.com/vuejs templates/webpack/issues/208#issuecomment 279959781 that suggests using relative paths. Test under three scenarios: requiring assets in JS vs CSS, working with vue router history mode, and code splitting. Examine the webpack configuration in the template, particularly the output.publicPath and loader options for url loader and file loader. Create a minimal reproduction and consider adding automated tests to cover these cases.
[Placeholder]: Clear up situation with assets paths in production for css-loader · vuejs-templates/webpack#1021 | Good First Issue