Replaces Webpack/Babel/Mocha with Vite/Vitest

[ralexmatthews]

Description

Sorry, I was a dummy and accidentally closed #484 by deleting my own fork 🙃 so this is the exact same code, just on an easypost branch.

I decided to start with a much smaller problem to tackle, so this only removes Webpack/Babel/Mocha with Vite/Vitest. I chose Vite/Vitest because that it what Easy-UI uses for its builds and tests.

There is a lot of files changed, but all changes are actually pretty minimal. All this does really is:

• Remove all webpack/babel/mocha dependencies and related files
• Installs Vite/Vitest and creates their config files
• Convert the tests to support Vitest
  • changes the way Polly is set up
  • remove all this. references in the tests
  • all cassettes work in place and none needed to change
• Makes some changes to github workflows
  • Adds a "test-node-compatibility" test that checks importing and using of the library
  • We don't want to just run the test suite because vite/vitest requires node v18+, but can generate output for arbitrarily low node versions

And thats effectively it. All commands still work as is. There are no changes to the source, and the output file is effectively the same. This does mean that it hasn't fixed any of the weird issues with using the project in Next.js and stuff. That can come at a later date since that will likely require breaking changes to fix.

Overall, this removes like half of the project's deps, and with it, the security vulnerabilities in exchange for a modern toolset.

Testing

All unit tests are passing. In added another test/check specifically for checking compatibility with older node versions. It basically just imports the project and tries to create a test shipment. This makes it so we can test compatibility with old node versions while not requiring the toolchain to support old node versions.

const EasyPostClient = require('../..');

const test = async () => {
  const client = new EasyPostClient('apiKey');

  if (!client.baseUrl.match(/^(http|https):\/\/api.easypost.com/gm)) {
    process.exit(1);
  }
};

test();

I also tested it with using actual API calls with a minimal project using node 12 and 22 and saw it working. I also checked node 10 and confirmed that did not work.

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)

[Justintime50]

@ralexmatthews if you can patch up the code scanning issue, I'll take a look

[ralexmatthews]

@Justintime50 fixed 👍

[ralexmatthews]

Dang it lol

[Justintime50]

Last time we attempted to overhaul the build system, we ran into issues once the final product was built, it couldn't be imported/referenced properly. Have we ensured that that issue is not a problem after these changes by running and E2E test by trying to import and use the final output of Vite?

[ralexmatthews]

Have we ensured that that issue is not a problem after these changes by running and E2E test by trying to import and use the final output of Vite?

Yea, I tested it with using actual API calls with a minimal project using node 12 and 22 and saw it working. I also checked node 10 and confirmed that did not work.

Also, thats what the node-compatibility CI check is supposed to check for.

So as far as I can tell, it has full compatibility with the current setup