ESM only

[pcfreak30]

I have been trying to use this with vite/5.4.9 and there seems to be some weird quirks around ESM. I have also tested vite 6.

I would request a transition to ESM only "type":"module" in a new semver and drop the dist folder too in all packages.

I am having to do

  resolve: {
    alias: {
      // Use the ESM version specifically
      "robot3": path.resolve(__dirname, "../../node_modules/robot3/machine.js"),
      "react-robot": path.resolve(
        __dirname,
        "../../node_modules/react-robot/machine.js",
      ),
    },
  },

commonjs({
      filter(id) {
        return (
          id.includes("url") ||
          id.includes("robot3") ||
          id.includes("react-robot")
        );
      },
    }),

 optimizeDeps: {
    include: ["robot3", "robot3/debug", "react-robot"],
  },

And I would prefer not to do such awkward vite configs.

Alternative you can do in all packages, only (remove main/module)

  "type":"module",
  "main": "machine.js",

and rely on exports for everything in-case any tooling wants to act differently. The whole standard is a mess to begin with, but this works with vite.

[matthewp]

I do agree with you about going ESM only, but we just released 1.0 a month ago so I don't want to make a breaking change for at least a few more months. In any event, we have the proper exports and this should be working: https://github.com/matthewp/robot/blob/main/packages/core/package.json#L10

If you can create a Stackblitz example showing it failing with Vite I'd consider that a p5 bug to fix immediately.

[smeijer]

AreTheTypesWrong shows that there are issues with the bundled output. That might be related to OPs problem.

https://arethetypeswrong.github.io/?p=robot3%401.1.1

In my experience, bundling with tshy is effortless, pain free, and guaranteed to have full CJS/ESM compatible outputs. I'd be happy to submit a PR switching the build setup to tshy, if you're open to that.

[matthewp]

@smeijer I'd be fine with that as temporary solution. But as discussed here, I want to go ESM-only in the next major. Is tshy still useful in that scenario?

[smeijer]

IMO it is. Using the dialects option you can make it output ESM-only, and it'll still make sure that your typescript definitions, and package.json#exports are correct.

That being said, I don't get why you'd go ESM-only when a hybrid works without extra effort.