Implementing on Node.js 16

[andraan]

Hi,

First of all, I would like to thank everyone for the effort put into this project and for the initiative to improve the code experience.

I have a question about the version compatibility of Node.js. We currently have a project with Node v16, and we plan to migrate from webpack to vite with the help of AEM-vite. However, we're encountering errors when executing npm install with a version of Node higher than 14 (it works fine with Node 14).

The error specifically occurs when installing the zlib library, which is a dependency of aem-vite-plugin. According to some research it's because zlib is now part of Nodejs (See docs here).

❯ npm install
npm WARN old lockfile 
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile 
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile 
npm WARN deprecated source-map-url@0.4.1: See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated source-map-resolve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated sourcemap-codec@1.4.8: Please use @jridgewell/sourcemap-codec instead
npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm ERR! code 127
npm ERR! path /react-vite/ui.frontend/node_modules/zlib
npm ERR! command failed
npm ERR! command sh -c -- node-waf clean || true; node-waf configure build
npm ERR! sh: node-waf: command not found
npm ERR! sh: node-waf: command not found

Has anyone else run into a similar error while installing? Or do you know of any procedures to use this aem-vite with Node.js version 16? It works fine when running with version 14 of Node.

Thank you all very much for your help, and please let me know if any additional information is needed.

[andraan]

Using the latest version (2.3.3) of @aem-vite/vite-aem-plugin solve the problem.