-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Upgrade to Formidable 3, Node 14, and audit fix #1192
Conversation
"module": "commonjs", | ||
"moduleResolution": "nodenext", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
needed to have import transpiled to import and not back to require
@@ -1,8 +1,9 @@ | |||
{ | |||
"compileOnSave": true, | |||
"compilerOptions": { | |||
"target": "es3", | |||
"target": "es2020", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
with node 12 drop, the target can be bumped to ES2020 (based on https://node.green)
4f63d1d
to
7dafcfa
Compare
@benasher44 please get the build to pass |
7dafcfa
to
9500758
Compare
Lint issue is fixed! |
Hi @jsdevel! I wanted to check in to see if it might be possible to merge and release this 🙏. Thanks for your support and consideration! |
Hi Team, |
Formidable 2 has a CVE that is flagged as requiring upgrading to Formidable 3. Formidable 3 is ESM only. To easily support this in node-soap without going through the full CommonJS -> ESM migration, we can do a dynamic import to load Formidable 3. This isn't a huge deal in this library, since the one place where Formidable 3 is used is async anyway.
TS didn't support correctly transpiling import calls until somewhat recently, so doing this required upgrading TypeScript. This also drops Node 12 support, which is EOL.
I also ran audit fix to get this library back to 0 audit issues.