Support convex.config.[cm]js and convex.config.d.[cm]ts

[prisis]

Currently convex components support only the .js and .d.ts extensions.

To support standard extensions for esm and cjs, convex should check if a convex.config does exists with .cts,.mts and .d.cts,.d.mts.

This is the place that needs the change

• convex-backend/npm-packages/convex/src/cli/lib/components/definition/bundle.ts

  Line 56 in 13a9716

  // "convex.config", "convex.config.js", "convex.config.ts", etc.

• convex-backend/npm-packages/dashboard-common/scripts/build-convexServerTypes.py

  Line 42 in 13a9716

  elif path.endswith(".d.ts"):

if im correct

[thomasballinger]

@prisis is there a reason you'd like these to be supported? convex.config.js must be esm format so there's no need to support .cjs, and components always use "type": "module" so the extension shouldn't be necessary.

If you're authoring components that's great, the interface is subject to change but we do want this to be accessible. See https://github.com/get-convex/templates/tree/main/template-component for the current recommended template. If there's something blocking you here would love to hear about it.

[prisis]

I've been working on a fork of the @convex-dev/agent package to extend its functionality.

My main goal was to move away from the complex configurations often required by tsc to handle both CommonJS and ESM outputs. The standard approach often leads to issues like:

• Including unnecessary files in the final package (e.g., vitest.js in the dist folder https://www.npmjs.com/package/@convex-dev/agent?activeTab=code).
• tsc struggling to correctly generate type definition files (.d.ts) for files that have both default and named exports.
• Needing extra package.json files in subdirectories just to declare the module type ("type": "module"), which adds clutter.
• There are a lot of edge cases, that tsc cant handle, one more would be the typesVersions key, generation.

To address this, I used a modern bundler, packem, which simplifies this process immensely. By using explicit file extensions (.mjs for ESM, .cjs for CommonJS) there are other like rolldown, tsup etc, the module type is clear, and the need for extra package.json files is eliminated.

This refactor, which you can see in my fork here, successfully reduced the package size from 2.93 MB to 2.2 MB (with esm and cjs support) with esm only support its 1.6 MB.

However, I've run into a blocker: Convex doesn't seem to recognize .mjs and .d.mts files. This prevents me from using this more modern, efficient package structure within the Convex environment.

[thomasballinger]

Ah thanks for the context, @ianmacartney mentioned this the other day, cool that you're looking at this.

More important than the package size, using more standard tools here would be great.

Ideally we could get some test coverage if we're changing things, https://github.com/get-convex/convex-backend/tree/main/npm-packages/private-demos/components-poc has some of this.

Some of this is a bit involved to change because the structure of components isn't officially spec'd out yet, and as you can see from this bundling code, finding component definitions in particular is pretty custom.

Yeah ESM-only is a good idea, that seems like a good way to build these.

I added comments to #127, would you consider supporting outputting ESM-only builds of package with "type": "module" in the package.json with .js extensions in packem?

[prisis]

If you can provide me some examples how you like to have it tested, i could add test for it