You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a sample where I build a npm package containing a react component and that I'm trying to use the package as a dependency in the target app. Repo maraf/dotnet-wasm-react and more details on the issue maraf/dotnet-wasm-react#6.
It works for production build, but it doesn't for react-scripts start.
It seems that the plugin generates an invalid code in this scenario.
The last line of code produces the error. The problem is the __nested_webpack_require_3181__, the "normal" __webpack_require__ has $Refresh$ configured correctly.
Any ideas?
The text was updated successfully, but these errors were encountered:
I get the same issue. My main project (Project A) has a dependency of Project B. Project B is not a React project but vanilla JS project. Webpack configuration of Project A have symlinks: true.
but Webpack's HMR of Project A expects __nested_webpack_require_xxxx__.$Refresh$.runtime in the bundled code.
I have a sample where I build a npm package containing a react component and that I'm trying to use the package as a dependency in the target app. Repo maraf/dotnet-wasm-react and more details on the issue maraf/dotnet-wasm-react#6.
It works for production build, but it doesn't for
react-scripts start
.It seems that the plugin generates an invalid code in this scenario.
The last line of code produces the error. The problem is the
__nested_webpack_require_3181__
, the "normal"__webpack_require__
has$Refresh$
configured correctly.Any ideas?
The text was updated successfully, but these errors were encountered: