chore: update import paths to use .js file extensions

[zckrs]

To follow #32, #33 and fix build for ESM

[CLAassistant]

All committers have signed the CLA.

[bryanhuhta]

👋 Hey @zckrs! Thanks for this contribution. I just merged some lint changes (requiring semicolons) which created a lot of conflicts with this PR. I also ran CI on this PR and it looks like specifying .js in the imports is breaking many of the tests. I am investigating this right now.

[zckrs]

Hi @bryanhuhta 👋

I just rebase on main and reapply diff

How can I help you to merge this ?

[bryanhuhta]

@zckrs I appreciate your patience 🙇

I validated this patch works on both a ESM project and a CJS one, but the test suite does not appreciate these changes. When I run the tests, I get lots of

 FAIL  test/profiler.test.ts
  ● Test suite failed to run

    Cannot find module '../src/index.js' from 'test/profiler.test.ts'

    > 1 | import Pyroscope from '../src/index.js';
        | ^
      2 | import express from 'express';
      3 | import busboy from 'busboy';
      4 | import { Profile } from 'pprof-format';

      at Resolver.resolveModule (node_modules/jest-resolve/build/resolver.js:324:11)
      at Object.<anonymous> (test/profiler.test.ts:1:1)

Presumably because there is a mismatch between how jest is configured to resolve modules and how the modules are built. I've been trying to find a solution, but my free time is limited. The only blocker to this change is making sure the test suite can run with these changes in place.

[zckrs]

In fact Jest doesn't have a good support for ESM :/

https://jestjs.io/docs/ecmascript-modules

[nwalters512]

@bryanhuhta since it seems like Jest is the blocker here, would y'all welcome a PR to rewrite the tests with Mocha, Vitest, or some other test runner of your choice that better supports modern JS features like ESM?

[nwalters512]

I went ahead and opened #94 to migrate to Vitest. Hopefully that can unblock proper ESM support.

[bryanhuhta]

@zckrs I just merged a few PRs which should unblock this PR (#94 is the real work horse here):

• Remove package lock.json #90
• Migrate from Jest to Vitest #94
• Remove separately-built types #95

Can you merge origin/main and fix the merge conflicts? I'll approve and merge this PR after that, then cut a new release.

[nwalters512]

I tested these changes locally on top of the latest main. Tests are passing, and the output in dist/ looks as it should! 🎉

Very excited to see this land. @bryanhuhta if @zckrs can't resolve the conflicts soon, you should be able to do so on his behalf and get this merged. If not, I'd (selfishly) suggest opening a new PR with conflicts resolved so that the next release isn't blocked.

[zckrs]

Hi,
Need to sleep but after that I will rebase from main branch 😉

[bryanhuhta]

@zckrs @nwalters512 I merged this and released v0.4.0. Let me know if there's any problems that arise!