-
Notifications
You must be signed in to change notification settings - Fork 10.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
You must provide the URL of lib/mappings.wasm by calling SourceMapConsumer.initialize
#35607
Comments
Been having a very similar error happen any time I make a syntax error like forgetting quotes around a string or missing a required prop on a component. Completely crashes my development server so I'm having to restart it frequently and troubleshooting becomes very difficult and time consuming. I don't understand it and google has not helped.
|
Can you try using Node.js v16? I'm pretty sure it's this issue: mozilla/source-map#454 We'll need to see what we do with this upstream dependency |
@LekoArts That did resolve it. New Macs ship with Node.js v18 |
Moving back to node.js 16 may not be a final solution, see #13713 and nodejs/node#42638. This issue could keep open |
We'll try to migrate away so that it works also on Node 18 |
SourceMapConsumer.initialize
Same as parcel-bundler/parcel#8005 ? Try forcing resolution |
This works for the time being on the latest version of Node.js |
I use node.js v18.0.0, set my
deleted the Does anyone have any other suggestions? |
maybe placing it as a dependency? |
@TheOtterlord That worked! Thank you. I added it as a depedency in my
|
if I'm using yarn workspaces to build a theme as described in this Gatsby guide and I'm running into this error, which |
Probably root because it should effect all workspaces. I'm not too familiar with dependency resolution for workspaces though, so they might work differently. |
Please try using |
Due to gatsbyjs/gatsby#35607, `gatsby develop` is broken on newer versions of NodeJS due to broken `source-map`. A workaround to force using a high enough version fixes this and has been added to the `devDependencies`.
* master: [sc-9148] [project] Reverted the changed in the top-level package.json; the fix was needed only in the Example's package.json. [sc-9148] [project] Tried a workaround for the lib/mappings.wasm error (gatsbyjs/gatsby#35607 (comment)), but no dice.
…sc-11674/update-to-ios-3-5-3 * sc-9148-idiomatic-plugin-dot-swift: [sc-9148] [project] Reverted the changed in the top-level package.json; the fix was needed only in the Example's package.json. [sc-9148] [project] Tried a workaround for the lib/mappings.wasm error (gatsbyjs/gatsby#35607 (comment)), but no dice. [sc-9148] [project] Tried a workaround for the lib/mappings.wasm error (gatsbyjs/gatsby#35607 (comment)), but no dice. [sc-9148] [project] Re-synced modules. [sc-9148] [project] Reverted the run script to be iOS-only. [sc-9148] [project] Docs. [sc-9148] [project] The run_example script now runs `gradlew assemble` for Android builds. [sc-9148] [refactor] Used a little more idiomatic Swift, meaning more guard statements, switches, and inferred types.
…nerate-plugin.m * sc-9148-idiomatic-plugin-dot-swift: (46 commits) [sc-9148] [project] Reverted the changed in the top-level package.json; the fix was needed only in the Example's package.json. [sc-9148] [project] Tried a workaround for the lib/mappings.wasm error (gatsbyjs/gatsby#35607 (comment)), but no dice. [sc-9148] [project] Tried a workaround for the lib/mappings.wasm error (gatsbyjs/gatsby#35607 (comment)), but no dice. [sc-9148] [project] Re-synced modules. bump package version to 3.4.2 bump iOS version bump versions update package-lock.json var name fix function name fix options class bump versions expose setForegroundServiceOptions add --commit-hooks false and --git-tag-version false to the npm version command move npm version bump up earlier Update circleci to convenience images. swap out strings with single quotes for consistency Github actions conditionals fail with double quotes add template files and workflow to automate native SDK version bumps fix permission prompts ...
This fixed everything: Stop server (ctrl+C) |
That worked! 👍 |
while the previous commit reminds devs to `nvm use` the officially-supported version of node.js this dependency workaround helps resolve an unneccessary gatsby crash on newer versions in the future see gatsbyjs/gatsby#35607 (comment) for background
Preliminary Checks
Please make sure that you verify each checkbox and follow the instructions for them.
This issue is not a duplicate. Before opening a new issue, please search existing issues: https://github.com/gatsbyjs/gatsby/issue *
This issue is not a question, feature request, RFC, or anything other than a bug report directly related to Gatsby. Please post those things in GitHub Discussions: https://github.com/gatsbyjs/gatsby/discussions *
Description
I have a new laptop and I am setting up my environment following the Gatsby tutorial.. I am running into issues when I get to the step to "Run your site locally" specifically with the
gatsby develop
command. I get a webpack error on two files.I have not made it to the step to make my first commit to my GitHub repo, so the repo linked is the new repo without my initial commit (not a Gatsby site).
Reproduction Link
https://github.com/benackles/whatsgatsby
Steps to Reproduce
gatsby develop
ERROR #98123 WEBPACK
errorsExpected Result
Successfully fire up locally
Actual Result
Environment
Config Flags
No response
The text was updated successfully, but these errors were encountered: