provide a esbuild workflow

[deleonio]

Before submitting an issue please:

• Check that you are using the latest version of Inferno. Either using our CDN @ Master or by checking the tags on NPM.
• Check that the bug has not been fixed in the latest development version. Use our CDN @ Edge.
• Check that the issue has not been brought up before on Github issues.

If you can, please distill your problem down and include a JSFiddle example for illustration. Also when requesting bug fix please include at least one test to avoid regression.

Issue Template

Observed Behaviour

Inferno is...

Expected Current Behaviour

Inferno should...

Inferno Metadata

macOS / Windowx / Linux
Safari / Chrome / Firefox / ...

[Jarred-Sumner]

Here's what I am doing:

build({
  inject: ["./jsx-shim.js"],
  jsxFactory: "createElement",
  jsxFragment: "Fragment",
  // ... rest of your esbuild config
})

export { createElement } from "inferno-create-element";
export { Fragment } from "inferno";

This doesn't handle error messages

[jhsware]

If you use const enums in your code there is an issue with esbuild that is worth being aware of (I don't think it is a show stopper for app development though). See #1545