Is your feature request related to a problem?
Some dependencies that are used are unable to be upgraded to their latest versions due to them becoming esm-only. This makes it so that the latest bug fixes, features, and vulnerability resolutions for these dependencies are unable to be used.
Describe the solution you'd like
We should convert this project from commonjs to esm so that we can upgrade to esm-only versions of dependencies.
Describe alternatives you've considered
It is potentially possible to import esm dependencies while remaining a commonjs project but it would require a lot of painful configuration and isn't the recommended best practice for node development.
Additional context
This change is necessary to complete #329 which allows us to remove an override that was set up to resolve a vulnerability in a transitive dependency. Switching to esm will likely cause issues with the jest testing setup that is currently implemented. If issues are encountered with running jest on esm it may be easier to switch from jest to vitest which has much better out of the box esm support. A switch to vitest should be tracked as part of a separate issue if conducted.
Is your feature request related to a problem?
Some dependencies that are used are unable to be upgraded to their latest versions due to them becoming esm-only. This makes it so that the latest bug fixes, features, and vulnerability resolutions for these dependencies are unable to be used.
Describe the solution you'd like
We should convert this project from commonjs to esm so that we can upgrade to esm-only versions of dependencies.
Describe alternatives you've considered
It is potentially possible to import esm dependencies while remaining a commonjs project but it would require a lot of painful configuration and isn't the recommended best practice for node development.
Additional context
This change is necessary to complete #329 which allows us to remove an override that was set up to resolve a vulnerability in a transitive dependency. Switching to esm will likely cause issues with the jest testing setup that is currently implemented. If issues are encountered with running jest on esm it may be easier to switch from jest to vitest which has much better out of the box esm support. A switch to vitest should be tracked as part of a separate issue if conducted.