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 (4,466 forks)batch import
enhancementhelp wanted

Repository metrics

Stars
 (9,721 stars)
PR merge metrics
 (No merged PRs in 30d)

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

Research direction
Investigate the conditions causing incorrect asset paths in production with css loader and url loader, focusing on relative paths, and propose a solution that handles assets in JS, CSS, vue router history mode, and code splitting.
Tech stack
javascriptvuecss
Domain
frontendbuild systemtooling
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
JavaScriptVue.jsWebpack
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30