-
Notifications
You must be signed in to change notification settings - Fork 60
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
The Fetch API is an experimental feature #526
Comments
Unfortunately not. This is an error given by Node, and not us. Since Node v18, the fetch API was implemented, and it's still an experimental feature hence the error. |
Oh ok, so is it correct that you have not changed anything and Node.js 18 has now simply replaced the old fetch function with the new API. |
That is correct, we haven't changed any code. There was never a builtin |
Due to octokit/request.js#526 and node-fetch/node-fetch#1566 we need to disable the experimental Fetch API introduced in Node.js 18.x.
…y module info (#179) - feat(source-terasology-module): custom source plugin to fetch Terasology module information - basic information: name, url, description, homepageUrl - include URL to custom `cover` image if defined - parse `module.txt` and enrich it with `tags` (also skip repos without 'module.txt' on branch 'develop') - include content of `README.md` - chore: build with `NODE_OPTIONS='--no-experimental-fetch'` to avoid warning about experimental Fetch API in Node 18.x (see octokit/request.js#526 and node-fetch/node-fetch#1566) - doc(source-terasology-module): document basic usage of the source plugin
Is it possible to disable the ExperimentalWarning "The Fetch API is an experimental feature." which is displayed since Node.js 18?
Current Node.js:
v18.9.0
with
--trace-warnings
:The text was updated successfully, but these errors were encountered: