Jest/TS config adjustments (allow for debugging tests in WebStorm)

[soboko]

🏆 Enhancements 🏠 Internal

These changes are necessary (AFAIK) for setting up a Jest configuration in WebStorm that allows for setting breakpoints while running tests. Tests still work the same from the command line.

Such a config looks like this for one test file:

...and for all tests:

to: @conglei @kristw @williaster

[codecov]

Codecov Report

Merging #77 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master    #77   +/-   ##
=====================================
  Coverage     100%   100%           
=====================================
  Files          67     67           
  Lines         744    744           
  Branches      130    130           
=====================================
  Hits          744    744

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b40189c...31d0c07. Read the comment docs.

[williaster]

Hey @soboko thanks for looking into this. All of our lib configuration lives in @data-ui/build-config so updates should go there.

That said -- the intention with build-config is to be replaced entirely with an airbnb open-source build config that has exact parity (sometime in Q1), so I’d like to not deviate far from that one (which does not use ts-jest). So I'm not sure about the best way around it, internally they would recommend using vs code, but you can ask in our internal #typescript channel to see if it's possible to set this up in Webstorm without ts-jest. Is there a reason you need to step through in an IDE vs the browser source view?

[soboko]

Hey @soboko thanks for looking into this. All of our lib configuration lives in @data-ui/build-config so updates should go there.

That said -- the intention with build-config is to be replaced entirely with an airbnb open-source build config that has exact parity (sometime in Q1), so I’d like to not deviate far from that one (which does not use ts-jest). So I'm not sure about the best way around it, internally they would recommend using vs code, but you can ask in our internal #typescript channel to see if it's possible to set this up in Webstorm without ts-jest.

Hmm, I can always keep this stashed locally and apply it as needed, not a huge deal.

Is there a reason you need to step through in an IDE vs the browser source view?

Mainly for running tests.