Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • G gulp
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 24
    • Issues 24
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 3
    • Merge requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gulp
  • gulp
  • Issues
  • #2409
Closed
Open
Issue created Jan 16, 2020 by Administrator@rootContributor

Option to disable loading of existing source maps for the source

Created by: stof

The old gulp-sourcemaps had a loadMaps setting to control whether existing maps should be loaded. Gulp 4 has a single setting in gulp.src which controls both enabling sourcemaps and loading existing ones.

This cause issues for me when npm packages ship their bundle files with a sourcemap while they don't ship their original source code at the same time (and so they have sourcemaps pointing to non-existent files). For such cases, I'd rather have my own source maps point me to their bundle file (that I know about) rather than to their source code (that I don't know about). I would be great if this feature could be available again.

What version of gulp are you using? 4.0.2

What versions of npm and node are you using? node 12.14.1 yarn 1.21.1

Assignee
Assign to
Time tracking