fix(plugin-engines): enforce Node.js 16

[scarf005]

Summary

• fixes 빌드 가이드에 사용 Node.js 버전이 명시되면 좋겠습니다. #425

Description

Contributing.md

added Node.js section with version 16 requirement.

.nvmrc

added .nvmrc with Node.js version 16 specified.

[vercel]

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

Name	Status	Preview	Updated (UTC)
stackflow-docs	✅ Ready (Inspect)	Visit Preview	Dec 4, 2023 1:26am

[2woongjae]

I agree to specify the version of Node.js that the package can be built on inside the Contributing.md.

Usually, the engines field in a package.json file indicates the version of Node.js on which the package works.
So it doesn't make sense to write the buildable version of the package in engines field.
That's why using yarn-plugin-engines doesn't seem appropriate.

Additionally, writing the Node.js version of the build environment in the .nvmrc file seems like a good idea considering the large number of nvm users.

[scarf005]

Usually, the engines field in a package.json file indicates the version of Node.js on which the package works.
So it doesn't make sense to write the buildable version of the package in engines field.
That's why using yarn-plugin-engines doesn't seem appropriate.

This makes sense, thanks for the insight.

[2woongjae]

LGTM