Engines node version

[nlkluth]

Description

As part of vercel projects node version audit, the engines field has been added to specify a node version for docs website

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Adding or updating CI (Actions)
• This change requires a documentation update

How Has This Been Tested?

Checklist: (Feel free to delete this section upon completion)

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My code follows the style guidelines of this project (I have run yarn prettier:apply)
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes (I have run yarn test)
• My changes generate no new warnings
• Any dependent changes have been merged and published in downstream modules

Screenshots (for visual changes):

[changeset-bot]

⚠️ No Changeset found

Latest commit: e9913a6

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
react-native-owl	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 14, 2025 7:39pm