GQL-23: Implements esbuild

[macrouch]

Overview

What is the feature?

Updates repo to use esbuild over webpack. Also updated test suite to use Vitest over Jest in order to update packages.

What areas of the application does this impact?

Builds, tests

Testing

Ensure npm start works, ensure npm test works.

Checklist

• I have added automated tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (a60de35) to head (f4d996e).

Additional details and impacted files

@@            Coverage Diff            @@
##              main      #104   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           87        89    +2     
  Lines         1882      1886    +4     
  Branches       222       222           
=========================================
+ Hits          1882      1886    +4     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[daniel-zamora]

Does this exclude handler.js files from the code coverage report and if so why is that necessary?

[macrouch]

It does exclude that file. Each test creates its own instance of ApolloServer, which is mostly all the handler does. There might be a way to test that file better, but we haven't spent the time to do that. This setting was copied from the previous setup, so the coverage report stays consistent.

[abbottry]

The only work that the handler does that isn't an external library is the acceptance of the authentication headers, that could be pulled into a util or something to make it testable. The important part of this is that the code is actually tested because it runs in many tests, its just the coverage is ignored.

[abbottry]

What does this do? It's a vastly different value than it was previously

[macrouch]

That is how we do the overrides in other apps, it tells npm to use the version of graphql we specified when we installed the package. So if we upgrade it at some point using $graphql keeps us from having to change this value to ^17

[abbottry]

Ah, neat.