Skip to content

Conversation

@irvinebroque
Copy link
Contributor

@irvinebroque irvinebroque commented Mar 5, 2025

We don't currently have one place where you can look at-a-glance at what Node.js APIs are supported in Workers.

The compatibility matrix here is very cool, but too detailed for a quick reference on what is or isn't supported:

https://workers-nodejs-compat-matrix.pages.dev/

The clearest thing we can do is to provide a simple list of all non-deprecated, non-experimental APIs from Node.js (pulled this straight from the Node.js docs, in the same alphabetical order) — and state clearly which are supported, which we have partial support for, and which are not supported. And then link to our own relevant docs page.

There are a few here that are currently supported, but we haven't yet added a docs page for. We'll need to follow up on this, so that the sidebar includes all of the Node.js APIs we currently support in the Workers Runtime.

We don't currently have one place where you can look at-a-glance at what Node.js APIs are supported in Workers.

The compatibility matrix here is very cool, overly detailed for a quick reference on what is or isn't supported:

https://workers-nodejs-compat-matrix.pages.dev/

The clearest thing we can do is to provide a simple list of all non-deprecated, non-experimental APIs from Node.js (pulled this straight from the Node.js docs, in the same alphabetical order) — and state clearly which are supported, which we have partial support for, and which are not supported. And then link to our own relevant docs page.

There are a few here that are currently supported, but we haven't yet added a docs page for. We'll need to follow up on this, so that the sidebar includes all of the Node.js APIs we currently support in the Workers Runtime.
@github-actions
Copy link
Contributor

github-actions bot commented Mar 5, 2025

Howdy and thanks for contributing to our repo. We review internal PRs within 1 week. If it's something urgent or has been sitting without a comment, start a thread in the Developer Docs space internally.

@github-actions
Copy link
Contributor

github-actions bot commented Mar 5, 2025

@irvinebroque
Copy link
Contributor Author

@anonrig @jasnell any edits? this accurate?

We can have auto-generated page too — but need something in our own docs that's digestable at a glance

@irvinebroque irvinebroque enabled auto-merge (squash) March 24, 2025 16:58
@hyperlint-ai
Copy link
Contributor

hyperlint-ai bot commented Mar 24, 2025

Howdy and thanks for contributing to our repo. The Cloudflare team reviews new, external PRs within two (2) weeks. If it's been two weeks or longer without any movement, please tag the PR Assignees in a comment.

We review internal PRs within 1 week. If it's something urgent or has been sitting without a comment, start a thread in the Developer Docs space internally.


PR Change Summary

Enhanced the Node.js documentation for Workers by providing a clear overview of supported APIs, including their status and links to relevant documentation.

  • Created a list of supported Node.js APIs in the Workers Runtime, indicating their support status.
  • Updated the section on enabling Node.js APIs to clarify configuration steps.
  • Improved the explanation of polyfills and their role in maximizing compatibility with npm packages.

Modified Files

  • src/content/docs/workers/runtime-apis/nodejs/index.mdx

How can I customize these reviews?

Check out the Hyperlint AI Reviewer docs for more information on how to customize the review.

If you just want to ignore it on this PR, you can add the hyperlint-ignore label to the PR. Future changes won't trigger a Hyperlint review.

Note specifically for link checks, we only check the first 30 links in a file and we cache the results for several hours (for instance, if you just added a page, you might experience this). Our recommendation is to add hyperlint-ignore to the PR to ignore the link check for this PR.

What is Hyperlint?

Hyperlint is an AI agent that helps you write, edit, and maintain your documentation.

Learn more about the Hyperlint AI reviewer and the checks that we can run on your documentation.

@irvinebroque irvinebroque merged commit d1c25e8 into production Mar 24, 2025
10 checks passed
@irvinebroque irvinebroque deleted the bib/node-js-progress branch March 24, 2025 17:35
RebeccaTamachiro pushed a commit that referenced this pull request Apr 21, 2025
* Enumerate Node.js APIs on main Node.js docs page

We don't currently have one place where you can look at-a-glance at what Node.js APIs are supported in Workers.

The compatibility matrix here is very cool, overly detailed for a quick reference on what is or isn't supported:

https://workers-nodejs-compat-matrix.pages.dev/

The clearest thing we can do is to provide a simple list of all non-deprecated, non-experimental APIs from Node.js (pulled this straight from the Node.js docs, in the same alphabetical order) — and state clearly which are supported, which we have partial support for, and which are not supported. And then link to our own relevant docs page.

There are a few here that are currently supported, but we haven't yet added a docs page for. We'll need to follow up on this, so that the sidebar includes all of the Node.js APIs we currently support in the Workers Runtime.

* Apply suggestions from code review

Co-authored-by: Yagiz Nizipli <[email protected]>

---------

Co-authored-by: Yagiz Nizipli <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

product:workers Related to Workers product size/s

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants