Add suport for esbuild 0.17

[handerss-spotfire]

This PR adds support for esbuild 0.17 by switching from the removed APIs to the new ones. I have also updated the peerDependencies and devDependencies to reflect this.

After making the appropriate changes 3 tests failed. I believe these fails may simply be due to changes in esbuild so I have tweaked the tests to make them pass, but please take a closer look. In particular the failing tests seem to be related to sourcemaps:

• sourcemap does not expect a source entry for env-ns or /tmp/.../*-bundle.js.
• sourcemap-base does not expect a source entry for env-ns.
• sourcemap-base-bundle has its error location moved (the new one seems correct to me).

Fixes: https://github.com/marvinhagemeister/karma-esbuild/issues/54

[handerss-spotfire]

The Ubuntu check failed due to some account limit. Guess this is unrelated to the PR?

error /home/runner/work/karma-esbuild/karma-esbuild/node_modules/sharp: Command failed.
Exit code: 1
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
Command: (node install/libvips && node install/dll-copy && prebuild-install) || (node-gyp rebuild && node install/dll-copy)
Arguments: 
Directory: /home/runner/work/karma-esbuild/karma-esbuild/node_modules/sharp
Output:
info sharp Downloading https://github.com/lovell/sharp-libvips/releases/download/v8.10.5/libvips-8.10.5-linux-x64.tar.br
ERR! sharp Status 503 Egress is over the account limit.
info sharp Attempting to build from source via node-gyp but this may fail due to the above error
info sharp Please see https://sharp.pixelplumbing.com/install for required dependencies

[jridgewell]

As a follow up, I think we can greatly simplify bundle.ts now that esbuild has the context API. A lot of the code we built up because we couldn't stop an in-progress build, and we couldn't be guaranteed the first build would return a proper BuildResult to issues rebuilds on. Both are solved with context.

[handerss-spotfire]

@jridgewell Sounds good, I just did the minimal amount of work to get it running.

[jridgewell]

Ping @marvinhagemeister to merge and release

[romanc]

@jridgewell / @marvinhagemeister any plans to merge this PR soon? Esbuild is moving quite fast and I would like to keep up with it. I'm thinking of creating a fork just to get this PR merged and get myself unblocked from updating eslint. I'm happy to do so, just want to make sure it's worth the "effort". If you guys plan to merge soon, I wouldn't need to do that.

[objerke]

@marvinhagemeister Any chance of this being merged? It would be a great improvement as this tool holds back usage of newer versions of esbuild and its new TypeScript/CSS bundling features.

[anthony-redFox]

Happy Friday - new fork https://www.npmjs.com/package/karma-esbuild-up

https://github.com/Second-Live/karma-esbuild-up

[angrycat9000]

Thanks for merging this @jridgewell . Any plans for a release with this fix?

[romanc]

FYI https://github.com/karma-runner/karma#karma-is-deprecated-and-is-not-accepting-new-features-or-general-bug-fixes

[Bnaya]

Any plans for release it? :)

[angrycat9000]

bump @marvinhagemeister any plans to release an update with this? Would be greatly appreciated. Thanks

[gecugamo]

@jridgewell @marvinhagemeister hello - is this project still maintained? Looks like there are a couple forks out there that have released the esbuild 0.17 fix, but would prefer to use this package for clear documentation. Any chance we can release an update with the esbuild 0.17 changes?