vuejs-templates/webpack

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

Open

#1,021 opened on Nov 1, 2017

View on GitHub
 (6 comments) (3 reactions) (0 assignees)JavaScript (9,721 stars) (4,466 forks)batch import
enhancementhelp wanted

Description

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.

Contributor guide

Tech stack
javascriptnodejscss
Domain
build systemfrontend
Issue type
research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
knowledge of webpack loadersunderstanding of CSS and JS asset pathsfamiliarity with vue router history modeexperience with code splitting
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
15
Research direction
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.