feat: support esbuild@0.15.x

[hughrawlinson]

What: Add esbuild@0.15.x to the list of peer dependencies.

Why: At the moment, npm install will fail when the version of esbuild included in the project is on the latest minor version.

How:

Checklist:

• [ ] Documentation
• [ ] Tests (maybe n/a)
• [X] Ready to be merged

I don't know how to test this. I haven't seen anything in the changelog that would indicate to me it wouldn't work, but then I don't know the internals. The changelog refers to backwards incompatible changes, but they are to do with moving to an internal implementation of Yarn's PlugnPlay algorithm. Any advice would be greatly appreciated.

[leon]

Any news on this?

[magoz]

Waiting for this to be merged too. Any updates?

[kentcdodds]

Sorry for the radio silence. This has been resolved.

[priyang12]

hi i thought this issue was resolved but when I installed latest version of the mdx-bundler I am still getting

      "peerDependencies": {
        "esbuild": "0.11.x || 0.12.x || 0.13.x || 0.14.x"
      }

  in package-lock.json file

Is there any other alternative like overriding it?

[kentcdodds]

Looks like the release failed to go through because the build is busted. I'm afraid I don't have time to fix it myself, but I'd accept a PR.

[priyang12]

i could make one but I don't know what to change since "esbuild": "0.*"is set in package.json. is the build pipeline failed is the reason for an issue not being fixed?

[kentcdodds]

The build pipeline failure is the reason it's not released.

[priyang12]

ok, I look into it if i can solve it. thanks for your reply.

[priyang12]

hey @kentcdodds i have made a PR 198

[github-actions[bot]]

:tada: This issue has been resolved in version 9.1.0 :tada:

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot :package::rocket: