vuejs/vue-cli

Weird issue with source maps

Open

#2978 opened on Nov 19, 2018

View on GitHub
 (32 comments) (39 reactions) (0 assignees)JavaScript (29,754 stars) (6,328 forks)batch import
enhancementhelp wantedscope: cli-service build

Description

Version

3.1.1

Reproduction link

https://github.com/farzadmf/vue-cli-sourcemap-issue

Node and OS info

Node 11.0.0 / yarn 1.12.3 / Windows 10

Steps to reproduce

  1. Run "yarn serve" to start the application
  2. Open Chrome devtools and start searching for "HelloWorld.vue"

What is expected?

When I search for HelloWorld.vue in Chrome devtools, I should see a single file being listed, and when I open that file, I should see my actual source code there

What is actually happening?

When I search for "HelloWorld.vue", I see multiple files being listed with names such as HelloWorld.vue?e24f ... (and a few others with different hash values)

  • I developed an app a few months ago with Vue, and I don't remember having this problem; maybe I've forgotten ...!
  • The version of vue-cli I have is 3.1.3, but it's not available in the drop-down
  • My Chrome version is 70.0.3538.102

Contributor guide

Tech stack
vuejavascript
Domain
frontenddeveloper experience
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.
1-3 hours
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.
mostly clear
Prerequisites
Basic Vue project setupUnderstanding of source maps
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45
Research direction
Investigate the reproduction repository provided (https://github.com/farzadmf/vue cli sourcemap issue). Compare the current behavior with expected behavior from older versions of vue cli. Look into webpack devtool configuration and how source maps are generated for single file components. Check if the issue is related to cache busting or webpack's module system adding query strings. Engage with the 32 comments to see if any workarounds or root causes have been identified.