Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: fix default npm install command for c4builder #87

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

drejkamikaza
Copy link

@drejkamikaza drejkamikaza commented Mar 11, 2024

Why
When you try to use the default install npm i -g c4builder method for c4builder, there is an error like in the issue: #50

What
I've done an upgrade of packages: npm audit fix
Removed the package zlib
Changed the required lib to node - zlib

How to use
If you want to use the fixed version then run:
npm pack - you will get the c4builder-0.2.17.tgz
Then you can install the package using: npm i -g c4builder-0.2.17.tgz

@drejkamikaza drejkamikaza marked this pull request as ready for review March 11, 2024 13:25
@vpopovec
Copy link

What do you mean by "Changed the required lib to node - zlib"?

When I tried to install the specific version of c4builder I received the following error:

npm warn tarball tarball data for file:c4builder-0.2.17.tgz (null) seems to be corrupted. Trying again.
npm warn tarball tarball data for file:c4builder-0.2.17.tgz (null) seems to be corrupted. Trying again.
npm error code ENOENT
npm error syscall open
npm error path /Users/viliam/c4builder-0.2.17.tgz
npm error errno -2
npm error enoent ENOENT: no such file or directory, open '/Users/viliam/c4builder-0.2.17.tgz'
npm error enoent This is related to npm not being able to find a file.
npm error enoent

@CesarCasanova
Copy link

CesarCasanova commented May 10, 2024

He means the c4builder for new node versions needs to be node:zlib, righ below:

Captura de pantalla 2024-05-10 a la(s) 3 39 19 p  m

And due to that , remove "zlib" dependency from package.json too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants