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

Invalid 'main' key #103

Open
gtsop-pf opened this issue Oct 15, 2021 · 4 comments
Open

Invalid 'main' key #103

gtsop-pf opened this issue Oct 15, 2021 · 4 comments

Comments

@gtsop-pf
Copy link

Expected Behavior

Simply run the program

Actual Behavior

Gor error for invalid 'main' key in package.json

Steps to Reproduce

po2json input.po outpuit.po

Additional Data

Can you please make a new release containing this latest fix?
51e2310

@creage
Copy link

creage commented Jan 5, 2022

@mikeedwards could you help us please with this?

@creage
Copy link

creage commented Jan 18, 2022

We can also use patch-package, but still...

@HarelM
Copy link

HarelM commented Feb 22, 2022

Can a new version be released please?
I have this warning as well...

@riteshjagga
Copy link

riteshjagga commented Mar 2, 2022

This issue happened when we wanted to upgrade Node 14 to Node 16.

The package.json field needs an update for the main field to have it working correctly with Node 16 as per this deprecation but until that happens, one can follow a workaround as explained here.

Before:

const childProcess = exec(`./node_modules/.bin/po2json app.po app.json --format=\'jed1.x\' -p`)

After:

const childProcess = exec(`node --no-deprecation ./node_modules/.bin/po2json app.po app.json --format=\'jed1.x\' -p`)

The above code is from the gulp file but it works if you run this command in the terminal 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

No branches or pull requests

4 participants