plugin-react 1.0.6 triggers sourcemap and deoptimisation error/warning messages in dev server #5438

lucsky · 2021-10-27T09:25:37Z

Describe the bug

In a Vite+React project using version 1.0.6 of plugin-react, running yarn run vite serve and then accessing the server triggers a bunch of the following error messages:

Sourcemap for "/Users/luc/Code/myproj/node_modules/.vite/react-dom.js" points to missing source files
Sourcemap for "/Users/luc/Code/myproj/node_modules/.vite/react.js" points to missing source files
Sourcemap for "/Users/luc/Code/myprojvite/react-router-dom.js" points to missing source files
(... and more)

Reproduction

yarn create vite --template react test
cd test
yarn install
yarn run vite serve --open

This will trigger the following messages for me, when doing this in my Desktop folder:

[BABEL] Note: The code generator has deoptimised the styling of /Users/luc/Desktop/test/node_modules/.vite/react-dom.js?v=5ffcdbe8 as it exceeds the max of 500KB.
Sourcemap for "/Users/luc/Desktop/test/node_modules/.vite/react.js" points to missing source files
Sourcemap for "/Users/luc/Desktop/test/node_modules/.vite/react_jsx-dev-runtime.js" points to missing source files
Sourcemap for "/Users/luc/Desktop/test/node_modules/.vite/react-dom.js" points to missing source files

Forcing use of version 1.0.5 of plugin-react "fixes" the error messages:

yarn add --dev @vitejs/plugin-react@1.0.5

System Info

System:
    OS: macOS 12.0.1
    CPU: (8) x64 Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz
    Memory: 1015.09 MB / 32.00 GB
    Shell: 3.3.1 - /usr/local/bin/fish
  Binaries:
    Node: 17.0.1 - /usr/local/bin/node
    Yarn: 1.22.17 - /usr/local/bin/yarn
    npm: 8.1.0 - /usr/local/bin/npm
  Browsers:
    Chrome: 95.0.4638.54
    Firefox: 93.0
    Firefox Developer Edition: 90.0
    Safari: 15.1
    Safari Technology Preview: 15.4
  npmPackages:
    @vitejs/plugin-react: ^1.0.0 => 1.0.6
    vite: ^2.6.4 => 2.6.12

Used Package Manager

yarn

Logs

No response

Validations

Follow our Code of Conduct
Read the Contributing Guidelines.
Read the docs.
Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
The provided reproduction is a minimal reproducible example of the bug.

The text was updated successfully, but these errors were encountered:

0xS4D · 2021-10-27T09:57:57Z

Same error here! :(

mattixittam · 2021-10-27T13:44:10Z

Seems to be fixed in this commit: 8556ffe

Not released yet though.

scott-lc · 2021-10-28T14:51:44Z

Still getting this same error w/ vite 2.6.13 + @vitejs/plugin-react 1.0.7 on a branch new, default Vite react-js app.

Sourcemap for "/private/tmp/test/node_modules/.vite/react.js" points to missing source files

With DEBUG="vite:sourcemap" npx vite

Sourcemap for "/private/tmp/test/node_modules/.vite/react.js" points to missing source files
  vite:sourcemap Missing sources:
  vite:sourcemap   /private/tmp/test/node_modules/.vite/dep:react +0ms
Sourcemap for "/private/tmp/test/node_modules/.vite/react_jsx-dev-runtime.js" points to missing source files
  vite:sourcemap Missing sources:
  vite:sourcemap   /private/tmp/test/node_modules/.vite/dep:react_jsx-dev-runtime +869ms
Sourcemap for "/private/tmp/test/node_modules/.vite/react-dom.js" points to missing source files
  vite:sourcemap Missing sources:
  vite:sourcemap   /private/tmp/test/node_modules/.vite/dep:react-dom +6ms

#5458

uipoet · 2021-10-28T16:51:21Z

Both 1.0.6 and 1.0.7 contain this regression.

runia1 · 2021-10-29T21:19:32Z

Can confirm 1.0.7 still has this issue

NazimHAli · 2021-11-01T11:45:45Z

+1 can confirm 1.0.7 has it as well.

jacksteamdev · 2021-11-01T18:59:56Z

Seems to be fixed in this commit: 8556ffe

8556ffe was released in 1.1.0-beta.0, but this issue is still present

ClarkXia · 2021-11-02T09:35:47Z

deoptimisation message cause by transform files which is larger than 500KB, it should be a way for developers to config rules of exclude babel transform when using plugin-react.

Mark24Code · 2021-11-03T09:11:46Z

I met same issues

    "@vitejs/plugin-react": "^1.0.7",
    "vite": "^2.6.13",

Not fixed

Sourcemap for "<**USER_PROJECT_PATH**>/node_modules/.vite/react.js" points to missing source files
Sourcemap for "<**USER_PROJECT_PATH**>/node_modules/.vite/react-dom.js" points to missing source files
Sourcemap for "<**USER_PROJECT_PATH**>/node_modules/.vite/react_jsx-dev-runtime.js" points to missing source files
Sourcemap for "<**USER_PROJECT_PATH**>/node_modules/.vite/prop-types.js" points to missing source files
[BABEL] Note: The code generator has deoptimised the styling of <**USER_PROJECT_PATH**>/node_modules/.vite/chunk-U3O7RQT4.js?v=a89d0a80 as it exceeds the max of 500KB.
[BABEL] Note: The code generator has deoptimised the styling of <**USER_PROJECT_PATH**>/node_modules/.vite/draft-js.js?v=a89d0a80 as it exceeds the max of 500KB.
Sourcemap for "<**USER_PROJECT_PATH**>/node_modules/.vite/draft-js.js" points to missing source files

danieltkach · 2021-11-03T11:30:37Z

What's the solution?

Niputi · 2021-11-03T11:51:00Z

please pin to version 1.0.5 and wait with upgrade until issue have been closed

danieltkach · 2021-11-03T14:20:03Z

please pin to version 1.0.5 and wait with upgrade until issue have been closed

How do I do this?

andy-law · 2021-11-03T14:22:54Z

@danieltkach Just change the dependency in your package.json from e.g. "@vitejs/plugin-react": "^1.0.0" to "@vitejs/plugin-react": "1.0.5" (remove the ^ and set it to a fixed version)

rwieruch · 2021-11-05T13:07:29Z

FYI: I removed node_module and yarn.lock, reinstalled everything with the pinned version 1.0.5, but still see these Sourcemap warnings.

My Vite dependencies are:

"vite": "^2.6.13",
"vite-plugin-svgr": "^0.4.0",
"@vitejs/plugin-react": "1.0.5

andy-law · 2021-11-05T13:15:27Z

@rwieruch which version of @vitejs/plugin-react do you see in you yarn.lock file? Is it possible that yarn somehow installed a cached version? Might be worth trying the same again but also run yarn cache clean before yarn (of course it shouldn't do this as you've locked the version, but just wondering if it's something along those lines)

kulothunganug · 2021-11-05T13:16:23Z

Me too encountering this, Is this is a serious issue?

sanyuan0704 · 2021-11-05T13:25:23Z

This problem has troubled me for a week, and now I finally find the cause!

sanyuan0704 · 2021-11-05T13:27:08Z

I will create a pull request to solve it right away.

sanyuan0704 · 2021-11-05T14:05:14Z

What's the solution?

Now i commit the solution. #5563

Closes vitejs#5438

templeman15 · 2021-11-09T07:48:46Z

@danieltkach Just change the dependency in your package.json from e.g. "@vitejs/plugin-react": "^1.0.0" to "@vitejs/plugin-react": "1.0.5" (remove the ^ and set it to a fixed version)

I have done this, deleted node_modules/.vite/ and can verify @vitejs/plugin-react@1.0.4 in yarn.lock. I'm still getting the same exact sourcemap warnings and babel deoptimized style warnings. Has anyone been successful by doing this?

memark · 2021-11-09T08:15:50Z

@templeman15 Please try using 1.0.5 (not .4) as instructed above.

templeman15 · 2021-11-09T09:27:00Z

@templeman15 Please try using 1.0.5 (not .4) as instructed above.

@memark im using vite-preset-react which only has a v2.0.0 that has a dependency of 1.0.4. Even if I explicitly add 1.0.5 to my package.json file it is still adding 1.0.4 through vite-preset-react. I'll try one more time in the morning. Thanks!

memark · 2021-11-09T09:56:04Z

@templeman15 I see. That's a (common) problem. Here is some discussion about the general case:
https://stackoverflow.com/questions/15806152/how-do-i-override-nested-npm-dependency-versions

More specifically here, you might want to ask the author of vite-preset-react to use 1.0.5 and link to this issue.
Or perhaps stop using that plugin (IMHO it doesn't add much you can't configure yourself with a few lines of code).

templeman15 · 2021-11-09T15:58:11Z

More specifically here, you might want to ask the author of vite-preset-react to use 1.0.5 and link to this issue. Or perhaps stop using that plugin (IMHO it doesn't add much you can't configure yourself with a few lines of code).

@memark thank you for writing back. I was able to do this through yarn with Selective dependency resolution

I just added this to package.json:

 "resolutions": {
    "@vitejs/plugin-react": "1.0.5"
  },

yarn install

And everything works perfect. I'm not sure why we're using vite-preset-react, I'll look into removing it!

rwieruch · 2021-11-12T09:03:18Z

@rwieruch which version of @vitejs/plugin-react do you see in you yarn.lock file? Is it possible that yarn somehow installed a cached version? Might be worth trying the same again but also run yarn cache clean before yarn (of course it shouldn't do this as you've locked the version, but just wondering if it's something along those lines)

we do not use vite-preset-react (just to make sure, because it was mentioned somewhere else)
in the package.json it says: "@vitejs/plugin-react": "1.0.5",
in the yarn.lock it says:

"@vitejs/plugin-react@1.0.5":
  version "1.0.5"
  resolved "https://registry.yarnpkg.com/@vitejs/plugin-react/-/plugin-react-1.0.5.tgz#8da501137078c8cb791cf2611f23de7b96ad5494"
  integrity sha512-n92p2fMlo0FZED+y5WYt+tM1mnQsVxcjZ8HuTJhv9gU/nW2zHwEoCemU78Az0KvF+bgafv2AdU4VEnP24bppvw==
  dependencies:

When I start the project, I still get the source map warnings. Since these are just warnings and the project runs without problems, I kept it like this for now.

rwieruch · 2021-11-12T09:12:07Z

Can confirm that the warnings go away with "@vitejs/plugin-react": "1.0.8",

Thanks @patak-js 🚀 👍🏽

memark · 2021-11-12T16:10:22Z

@rwieruch The bug has been fixed. Upgrade to 1.0.8 and it should go away.

Fixes #129 Updating the version of `@vitejs/plugin-react` removes the warnings about missing source files. See vitejs/vite#5438 (comment). I also was seeing these warnings, and updating made them disappear.

lucsky added the pending triage label Oct 27, 2021

lucsky changed the title ~~plugin-react 1.0.6 upgrade triggers sourcemap error/warning messages in dev server~~ plugin-react 1.0.6 upgrade triggers sourcemap and deoptimisation error/warning messages in dev server Oct 27, 2021

lucsky changed the title ~~plugin-react 1.0.6 upgrade triggers sourcemap and deoptimisation error/warning messages in dev server~~ plugin-react 1.0.6 triggers sourcemap and deoptimisation error/warning messages in dev server Oct 27, 2021

Niputi mentioned this issue Oct 28, 2021

React template project: Sourcemap for "/node_modules/.vite/react.js" points to missing source files #5458

Closed

7 tasks

bastiW mentioned this issue Oct 28, 2021

Sourcemap error after creating empty React TypeScript vite project .vite/react.js points to missing source files #5463

Closed

Shinigami92 added the regression The issue only appears after a new release label Oct 28, 2021

Niputi mentioned this issue Nov 5, 2021

Sourcemap for "xxxx" points to missing source files #5562

Closed

7 tasks

sanyuan0704 mentioned this issue Nov 5, 2021

fix: sourcemap error with plugin-react #5563

Closed

9 tasks

aleclarson added a commit to aleclarson/vite that referenced this issue Nov 8, 2021

fix(sourcemap): tolerate virtual modules in sources array

8be81db

Closes vitejs#5438

aleclarson mentioned this issue Nov 8, 2021

fix(sourcemap): tolerate virtual modules in sources array #5587

Merged

patak-dev closed this as completed in #5587 Nov 9, 2021

This was referenced Nov 17, 2021

Support features.storyStoreV7 storybookjs/builder-vite#126

Merged

Update @vitejs/plugin-react to avoid sourcemap warning storybookjs/builder-vite#153

Merged

yasiraslam0 mentioned this issue Nov 17, 2021

Internal server error: (0 , import_vite.transformWithEsbuild) is not a function #5722

Closed

7 tasks

frandiox mentioned this issue Nov 19, 2021

fix(plugin-react): remove querystring from sourcemap filename #5760

Merged

9 tasks

github-actions bot locked and limited conversation to collaborators Nov 27, 2021

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

plugin-react 1.0.6 triggers sourcemap and deoptimisation error/warning messages in dev server #5438

plugin-react 1.0.6 triggers sourcemap and deoptimisation error/warning messages in dev server #5438

lucsky commented Oct 27, 2021

0xS4D commented Oct 27, 2021

mattixittam commented Oct 27, 2021

scott-lc commented Oct 28, 2021 •

edited

Loading

uipoet commented Oct 28, 2021

runia1 commented Oct 29, 2021

NazimHAli commented Nov 1, 2021

jacksteamdev commented Nov 1, 2021 •

edited

Loading

ClarkXia commented Nov 2, 2021 •

edited

Loading

Mark24Code commented Nov 3, 2021 •

edited

Loading

danieltkach commented Nov 3, 2021

Niputi commented Nov 3, 2021

danieltkach commented Nov 3, 2021

andy-law commented Nov 3, 2021

rwieruch commented Nov 5, 2021

andy-law commented Nov 5, 2021

kulothunganug commented Nov 5, 2021

sanyuan0704 commented Nov 5, 2021

sanyuan0704 commented Nov 5, 2021

sanyuan0704 commented Nov 5, 2021

templeman15 commented Nov 9, 2021

memark commented Nov 9, 2021

templeman15 commented Nov 9, 2021

memark commented Nov 9, 2021

templeman15 commented Nov 9, 2021

rwieruch commented Nov 12, 2021

rwieruch commented Nov 12, 2021

memark commented Nov 12, 2021

plugin-react 1.0.6 triggers sourcemap and deoptimisation error/warning messages in dev server #5438

plugin-react 1.0.6 triggers sourcemap and deoptimisation error/warning messages in dev server #5438

Comments

lucsky commented Oct 27, 2021

Describe the bug

Reproduction

System Info

Used Package Manager

Logs

Validations

0xS4D commented Oct 27, 2021

mattixittam commented Oct 27, 2021

scott-lc commented Oct 28, 2021 • edited Loading

uipoet commented Oct 28, 2021

runia1 commented Oct 29, 2021

NazimHAli commented Nov 1, 2021

jacksteamdev commented Nov 1, 2021 • edited Loading

ClarkXia commented Nov 2, 2021 • edited Loading

Mark24Code commented Nov 3, 2021 • edited Loading

danieltkach commented Nov 3, 2021

Niputi commented Nov 3, 2021

danieltkach commented Nov 3, 2021

andy-law commented Nov 3, 2021

rwieruch commented Nov 5, 2021

andy-law commented Nov 5, 2021

kulothunganug commented Nov 5, 2021

sanyuan0704 commented Nov 5, 2021

sanyuan0704 commented Nov 5, 2021

sanyuan0704 commented Nov 5, 2021

templeman15 commented Nov 9, 2021

memark commented Nov 9, 2021

templeman15 commented Nov 9, 2021

memark commented Nov 9, 2021

templeman15 commented Nov 9, 2021

rwieruch commented Nov 12, 2021

rwieruch commented Nov 12, 2021

memark commented Nov 12, 2021

scott-lc commented Oct 28, 2021 •

edited

Loading

jacksteamdev commented Nov 1, 2021 •

edited

Loading

ClarkXia commented Nov 2, 2021 •

edited

Loading

Mark24Code commented Nov 3, 2021 •

edited

Loading