chore(.nvmrc): add node version v20.18.0

[sukvvon]

Description

• added an .nvmrc file to specify the node.js version in a project where it was not previously defined. this addition ensures a consistent node.js version across development and deployment environments. additionally, the node-version parameter in actions/setup-node within github actions has been replaced with node-version-file: '.nvmrc' to support version management based on the configuration file.

Changes

• added an .nvmrc file at the project root to specify the node.js version.
• replaced the node-version option in actions/setup-node with node-version-file: '.nvmrc' in github actions.

Motivation and Context

• the project previously lacked a defined node.js version, leading to potential inconsistencies when different developers use varying versions. this can cause unexpected errors or compatibility issues in some environments. adding an .nvmrc file provides a clear definition of the node.js version, reducing the likelihood of such issues. additionally, updating the github actions configuration allows for consistent versioning in the ci environment, enhancing overall reliability.

How Has This Been Tested?

• verified that adding the .nvmrc file allows the specified node.js version to be used in the local development environment via the nvm use command.

Screenshots (if appropriate):

Types of changes

• [ ] 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 change)
• [ ] Documentation update

Checklist

• [x] I have performed a self-review of my own code.
• [ ] My code is commented, particularly in hard-to-understand areas.
• [ ] I have made corresponding changes to the documentation.
• [x] My changes generate no new warnings.
• [ ] 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.
• [ ] Any dependent changes have been merged and published in downstream modules.

Further Comments

[changeset-bot[bot]]

⚠️ No Changeset found

Latest commit: c2243d787aab4eda9ffe66f711c80a8d88fa9610

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[bot]]

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

Name	Status	Preview	Comments	Updated (UTC)
overlay-kit	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 17, 2024 0:38am

[sukvvon]

@jungpaeng could you review this pr? 🙇🏻‍♂️