Encountering Node.js version mismatch, I need to force package installation. Try this workaround:
initInstall('libB', 'v2.3.4');
hey i solved it by setting the env variable npm_config_engine_strict=false when installing. worked for me without tweaking any files so it might just do the trick. just double-check your app after install, as things may go a bit sideways.
hey i fixed it by temporarily removing the engine chk from package.json then using npm install --force. sure its a hack but it worked fine in my case, so give it a try
I encountered a similar issue and resolved it by configuring npm to ignore the engine check. In my project I used the command npm config set engine-strict false before installing dependencies, which allowed the process to complete successfully. An alternative approach I tried involved leveraging the --legacy-peer-deps flag to bypass strict checks during installation. It is important to note that bypassing these safeguards might lead to unexpected behavior later, so careful testing on your specific setup is recommended to ensure full compatibility of the package with your Node.js version.
In my experience, the safest workaround was to use an .npmrc file to bypass the stricter engine check without directly modifying package.json. I added a configuration to set engine-strict to false, which allowed the installation to complete while still maintaining control over dependency behavior. I also tested the application thoroughly after bypassing the check to ensure that everything functioned as expected. This method worked consistently for me and avoided potentially risky edits to package.json, making it a viable option for handling version mismatches.