Could not read source map: vue-global-config.mjs.map

[AlexNastold]

Before you start, please make sure to:

• [X] Read the document
• [X] Have tried the latest version
• [X] Search to see if your issue already exists
• [X] Look for Q&A through appropriate channels like Stack Overflow

Link to minimal reproduction

https://github.com/AlexNastold/json-editor-vue-bug

Validation

• [X] ⚠ I understand that invalid, incomplete or superfluous reproduction can lead to this issue being closed

Describe the bug and steps to reproduce

Could not read source map for file:///home/anastold/git-projects/admin-dashboard-ng2/node_modules/.pnpm/json-editor-vue%400.15.1_%40lezer%2Bcommon%401.2.1_vue%403.4.27_typescript%405.4.5_/node_modules/json-editor-vue/node_modules/.pnpm/vue-global-config%400.6.1_%40vue%2Bcomposition-api%401.7.2_vue%403.4.26_typescript%405.4.5___vue%403.4.26_typescript%405.4.5_/node_modules/vue-global-config/dist/vue-global-config.mjs: ENOENT: no such file or directory, open '/home/anastold/git-projects/admin-dashboard-ng2/node_modules/.pnpm/json-editor-vue@0.15.1_@lezer+common@1.2.1_vue@3.4.27_typescript@5.4.5_/node_modules/json-editor-vue/node_modules/.pnpm/vue-global-config@0.6.1_@vue+composition-api@1.7.2_vue@3.4.26_typescript@5.4.5___vue@3.4.26_typescript@5.4.5_/node_modules/vue-global-config/dist/vue-global-config.mjs.map'

1. Clone repository
2. Install dependencies
3. Run "pnpm dev"
4. Start chrome or edge with vscode "run and debug"
5. Look at vscodes "DEBUG CONSOLE"

System Info

System:
    OS: Linux 4.18 Red Hat Enterprise Linux 8.4 (Ootpa)
    CPU: (4) x64 Intel(R) Xeon(R) Gold 6240 CPU @ 2.60GHz
    Memory: 7.10 GB / 15.65 GB
    Container: Yes
    Shell: 5.5.1 - /usr/bin/zsh
  Binaries:
    Node: 20.11.0 - ~/.nvm/versions/node/v20.11.0/bin/node
    npm: 10.2.4 - ~/.nvm/versions/node/v20.11.0/bin/npm
    pnpm: 9.0.6 - ~/.nvm/versions/node/v20.11.0/bin/pnpm
  npmPackages:
    @popperjs/core: ^2.11.8 => 2.11.8 
    @tinymce/tinymce-vue: ^5.1.1 => 5.1.1 
    @tsconfig/node20: ^20.1.4 => 20.1.4 
    @types/bootstrap: ^5.2.10 => 5.2.10 
    @types/humanize-duration: ^3.27.4 => 3.27.4 
    @types/jquery: ^3.5.29 => 3.5.30 
    @types/node: ^20.12.8 => 20.12.11 
    @types/uuid: ^9.0.8 => 9.0.8 
    @vite-pwa/assets-generator: ^0.2.4 => 0.2.4 
    @vitejs/plugin-vue: ^5.0.4 => 5.0.4 
    @vue/eslint-config-prettier: ^9.0.0 => 9.0.0 
    @vue/eslint-config-typescript: ^13.0.0 => 13.0.0 
    @vue/tsconfig: ^0.5.1 => 0.5.1 
    archiver: ^7.0.1 => 7.0.1 
    autoprefixer: ^10.4.19 => 10.4.19 
    axios: ^1.6.8 => 1.6.8 
    bootstrap: 5.3.3 => 5.3.3 
    bootstrap-icons: ^1.11.3 => 1.11.3 
    chalk: ^5.3.0 => 5.3.0 
    chart.js: ^4.4.2 => 4.4.2 
    corejs-typeahead: ^1.3.4 => 1.3.4 
    datatables.net: ^2.0.5 => 2.0.7 
    datatables.net-bs5: ^2.0.5 => 2.0.7 
    datatables.net-buttons: ^3.0.2 => 3.0.2 
    datatables.net-buttons-bs5: ^3.0.2 => 3.0.2 
    datatables.net-fixedcolumns-bs5: ^5.0.0 => 5.0.0 
    datatables.net-plugins: ^2.0.5 => 2.0.7 
    datatables.net-responsive-bs5: ^3.0.2 => 3.0.2 
    datatables.net-scroller-bs5: ^2.4.1 => 2.4.2 
    datatables.net-vue3: ^3.0.1 => 3.0.1 
    dayjs: ^1.11.11 => 1.11.11 
    eslint: ^8.56.0 => 8.57.0 
    eslint-plugin-vue: ^9.25.0 => 9.25.0 
    flag-icons: ^7.2.1 => 7.2.1 
    https-proxy-agent: ^7.0.4 => 7.0.4 
    humanize-duration: ^3.32.0 => 3.32.0 
    i18next: 23.11.3 => 23.11.3 
    i18next-vue: ^4.0.0 => 4.0.0 
    inquirer: ^9.2.20 => 9.2.20 
    jquery: ^3.7.1 => 3.7.1 
    js-file-download: ^0.4.12 => 0.4.12 
    json-editor-vue: ^0.15.1 => 0.15.1 
    knip: ^5.11.0 => 5.13.0 
    machina: ^4.0.2 => 4.0.2 
    node-fetch: ^3.3.2 => 3.3.2 
    npm-check-updates: ^16.14.20 => 16.14.20 
    npm-run-all: ^4.1.5 => 4.1.5 
    pinia: ^2.1.7 => 2.1.7 
    prettier: ^3.2.5 => 3.2.5 
    rollup-plugin-license: ^3.3.1 => 3.3.1 
    rollup-plugin-visualizer: ^5.12.0 => 5.12.0 
    sass: ~1.76.0 => 1.76.0 
    sharp: ^0.33.3 => 0.33.3 
    stylelint: ^16.5.0 => 16.5.0 
    stylelint-config-standard-scss: ^13.1.0 => 13.1.0 
    stylelint-config-standard-vue: ^1.0.0 => 1.0.0 
    svgo: ^3.2.0 => 3.3.0 
    throttle-debounce: ^5.0.0 => 5.0.0 
    tinymce: ^7.0.1 => 7.1.0 
    typescript: ~5.4.5 => 5.4.5 
    unplugin-auto-import: ^0.17.5 => 0.17.5 
    uuid: ^9.0.1 => 9.0.1 
    vite: ^5.2.11 => 5.2.11 
    vite-plugin-image-optimizer: ^1.1.7 => 1.1.7 
    vite-plugin-pwa: ^0.20.0 => 0.20.0 
    vite-plugin-vue-devtools: ^7.1.3 => 7.1.3 
    vue: ^3.4.26 => 3.4.27 
    vue-chartjs: ^5.3.1 => 5.3.1 
    vue-datepicker-next: ^1.0.3 => 1.0.3 
    vue-router: ^4.3.2 => 4.3.2 
    vue-scrolling-table: ^2.0.0 => 2.0.0 
    vue-tsc: ^2.0.16 => 2.0.16 
    vue3-toastify: ^0.2.1 => 0.2.1 
    vuedraggable: 4.1.0 => 4.1.0 
    workbox-window: ^7.1.0 => 7.1.0

Package Manager

pnpm

[cloydlau]

Can't reproduce.

[cloydlau]

It's empty.

[cloydlau]

https://github.com/microsoft/vscode/issues/102335

I think you should upgrade your VSCode and disable all installed extensions, then retry.

[AlexNastold]

Important is step 4:

[cloydlau]

Still, everything is fine.

[AlexNastold]

Strange - your output in the "debug console" ist my output in "terminal". In "debug console" there is only the message from browser console:

Perhaps try with "pnpm dev" in integrated terminal and then start only the browser with "run and debug". Launch.json is the .vscode directory.

[cloydlau]

What is the result after upgrading VSCode to the latest version and disabling all extensions? Plus resetting the settings to the default if possible.

[AlexNastold]

VSCode is the latest version. Disabling all extensions change nothing. Still the same error.

[cloydlau]

If you do a search you'll find that there are tons of Could not read source map errors around VSCode, you should first rule out that it's not caused by VSCode or VSCode's configuration, e.g. first of all, reset your configuration (you can back it up first).

[cloydlau]

Close now due to inactivity. If there are any updates please just reply directly, no need to reopen a new one.

[AlexNastold]

Finally the addition of "resolveSourceMapLocations" in my launch.json fixed it - the weird thing is, that wasn't a problem in the past and no other dependencies seemed to make any problems.

Sorry for wasting your time, but anyway, thank you very much for checking.