-
Notifications
You must be signed in to change notification settings - Fork 20
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
Switch project to ESM in order to cover CVE on got package #27
Comments
Hi @ehmad11! Thanks for your quick feedback! I have worked a bit on But then any project that is relying on
What is the best option here? Force ESM migration for all ? I am a newbie on CJS/ESM stuff 😅 thinking of starting a brand new TS project for that 🤓 |
I will now get a look at the OK here is the PR on |
@ehmad11 I can take some resp. / ownership on both projects if you don't have time / access to a Netsuite system to run tests. Let me know! I would like also to provide types (so probably migrate the projects to TS !) |
@julbrs, just saw your package; it looks great. I am thinking, can we keep this current package as it is? Many projects depend on it, and switching to ESM would be a breaking change for them. We can put a deprecated notice in this package and advise users to use your package for future updates. I would really appreciate it if we could keep the new package as a fork of the current repo to preserve the commit history and contributions of other members with full credits. |
and yes we can merge the suiteql, it is a great idea |
That's a very good idea! I have take rebuilt the new repository here: https://github.com/julbrs/netsuite-api-client which is a github fork of https://github.com/ehmad11/netsuite-rest ( because there is more contribution in this one). I have also added a specific section in the README to explain the ESM/CommonJS stuff, with links to Thanks ! |
Hi @ehmad11
There is some CVE on the got package.
Are you available to merge and publish if I suggest a PR to handle this issue ?
Thanks!
The text was updated successfully, but these errors were encountered: