vuejs-templates/webpack

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

Open

#1.021 geöffnet am 1. Nov. 2017

Auf GitHub ansehen
 (6 Kommentare) (3 Reaktionen) (0 zugewiesene Personen)JavaScript (9.721 Stars) (4.466 Forks)batch import
enhancementhelp wanted

Beschreibung

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
SchwierigkeitGeschätzte Implementierungsschwierigkeit für neue Contributors, von 1 für sehr kleine Änderungen bis 5 für Expertenarbeit.
4
Geschätzte ZeitEin grober Zeitrahmen, um zu recherchieren, zu implementieren, zu testen und einen Pull Request vorzubereiten.
over 1 week
AktivitätsstatusWie verfügbar das Issue gerade wirkt: frisch, aktiv, stale, blockiert oder wartet auf Maintainer-Input.
stale
KlarheitWie klar das Issue die erwartete Änderung, Akzeptanzkriterien und den nächsten Schritt erklärt.
needs investigation
Voraussetzungen
knowledge of webpack loadersunderstanding of CSS and JS asset pathsfamiliarity with vue router history modeexperience with code splitting
EinsteigerfreundlichkeitEin Score von 1 bis 100, der schätzt, wie zugänglich dieses Issue für First-Time Contributors ist.
15
Research-Richtung
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.