[kac-axelor]

Why

When a Next.js app consumes the goovee-generated client, the bundler mangles the generated code, breaking entity class names and TypeORM metadata. The current workaround in consumer apps is to build with next build --no-mangling, which disables mangling globally — overkill for a problem that only affects one set of files.

The cleaner fix is to put the generated code somewhere the bundler treats as an external package, e.g. via Next.js serverExternalPackages. That requires the output to look like a real installable package: it must live under a resolvable name and ship a valid package.json.

This PR makes that possible without forcing every consumer to hand-write a package.json next to their generated files.

What changed

When schema.transpile is truthy, the generator now:

1. Writes a package.json into outDir describing the generated module — name, version, type, and exports for ./models and ./client. type is derived from transpile.module (commonjs → commonjs, otherwise module), so ESM/CJS output stays consistent.

2. Emits .js extensions on relative import specifiers. Node's ESM resolver requires explicit extensions and does not perform directory-index resolution; the .js form also works under CJS. Without this, the transpiled output cannot run under Node directly.

3. Imports ../models/index instead of ../models in the client entry point, for the same Node-ESM reason.

A new transpile.packageName option lets users override the default package name (@goovee/generated).

What did not change

When schema.transpile is unset or false, behavior is identical to before this PR:
raw .ts files are emitted to outDir with extensionless relative imports, and no package.json is written. Existing users who don't opt into transpile see no difference.

Consumer setup

In goovee.config.json:

{
  "schema": {
    "outDir": "node_modules/@goovee/generated",
    "transpile": true
  }
}

In next.config.mjs:

const nextConfig = {
  serverExternalPackages: ["@goovee/generated"],
  // ...
};

To use a different package name:

{
  "schema": {
    "outDir": "node_modules/@myorg/db-client",
    "transpile": { "packageName": "@myorg/db-client" }
  }
}

Monorepo setup

repo/
├─ apps/
│  └─ web/
├─ packages/
│  └─ db/
└─ pnpm-workspace.yaml

In goovee.config.json:

{
  "schema": {
    "outDir": "packages/db",
    "transpile": { "packageName": "@myorg/db" }
  }
}

In apps/web/package.json:

{
  "dependencies": {
    "@myorg/db": "workspace:*"
  }
}

In apps/web/next.config.mjs:

const nextConfig = {
  serverExternalPackages: ["@myorg/db"],
};

[kac-axelor]

#18 This fixes mangling which got merged , hence this feature is obsolete.