Removes Webpack/Babel in favor of SWC

[ralexmatthews]

Description

In its current state, the node library uses a webpack + babel build pipeline to bundle the whole library into one big CommonJS bundle. It uses maybe a dozen different webpack and babel settings, configs, plugins, etc to do this as well. This is probably not ideal for several reasons.

• Since this should only be used in Node.js, not in the browser, this does not need bundled, so Webpack isn't needed altogether
• Babel, while popular, isn't super fast, and has lots of plugins needed to get the settings we want

Enter SWC, the Babel replacement written in Rust. It is a dependency of Turbopack, Vercel's new transpiler/bundler for Next.js, and seems to be the current future.

As part of this move to SWC, I have also created both a CommonJS and ES6 build of the app to support the movement of the community away from CommonJS.

Getting rid of all the babel deps also removes these warnings when running npm install:

npm WARN deprecated @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-export-namespace-from instead.
npm WARN deprecated @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-properties instead.
npm WARN deprecated @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-unicode-property-regex instead.
npm WARN deprecated [email protected]: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.

Overall, this greatly reduces the number of dependencies, config files, and improves support for CJS and ESM projects.

Also fixes #446. I was able to replicate the error by creating a new Nest app, and by changing the version to this, it fixes that error.

Also fixes #456 by exporting all errors and models from the root.

Testing

All tests are still passing, thanks to swapping out babel/register to swc-node/register

Pull Request Type

Please select the option(s) that are relevant to this PR.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Improvement (fixing a typo, updating readme, renaming a variable name, etc)

[ralexmatthews]

I don't think we actually care that you can build, test, and generally dev on the project in Node.js 12. This builds the app on a modern version, then uses the older version to run a small script that imports and attempts to use the lib.

[Justintime50]

praise: I'm ecstatic to see this! 😃 Solid work, babel and webpack have been the bane of this lib for years...

Curious, does this break anything? I looked into removing babel a couple years back and it got very angry at me, it's possible that over the last couple years and the various refactors we've done we've slowly ripped out anything that previously was a problem but did want to check if there were any implications. We did previously remove the ability for this to run in the browser which may have been the sole thing needed to unblock this.

[Justintime50]

question: I assume this replaces the index.js file in the root? This accomplishes the same results though allowing users to require the entire library?

[ralexmatthews]

Yea, exactly. Starting in Node v12, you can use the conditional exports to specify what they should get when they use your package. Basically for both the CJS and ESM builds, the entire src directory is built and built in these folders, so if they are using an import EasyPostClient from "@easypost/api" it will import the "import"/esm build, and for older projects that do a const EasyPostClient = require("@easypost/api") it will use the "require"/cjs built assets.