Use un-buildable lib with TS logic (enums/constants/interfaces) only

[vkouk]

Summary

Hello all,

As title says I am trying to make a non-buildable lib that will hold all of my enums, interfaces etc in separate libs all of them. These will be reused to my monorepo for nestjs and angular 19 separately.

Now my question is, will this work or shall i mark them buildable like the rest of my libs?

This is my package json of my enums

{
    "name": "@repo-common/enums",
    "version": "0.0.0",
    "private": true,
    "license": "MIT",
    "main": "./src/index.ts",
    "scripts": {
        "lint": "eslint  --max-warnings 0",
        "check-types": "tsc --noEmit"
    },
    "publishConfig": {
        "access": "public"
    },
    "exports": {
        ".": "./src/index.ts"
    },
    "dependencies": {},
    "devDependencies": {}
}

This is my src/index.ts

export * from "./client";

This is my client/index.ts

export * from "./client-options.enum";

And this is my enum

export enum ClientOptions {
    IsChain = 0
}

On the other side of my nestjs app I am just using it as console.log

 console.log(
      {sChain: ClientOptions.IsChain }

Will this work or it must be buildable? Currently I get this error

Error [ERR_UNSUPPORTED_DIR_IMPORT]: Directory import '/clean/packages/enums/src/client' is not supported resolving ES modules imported from /clean/packages/enums/src/index.ts

Thanks a lot

Additional information

No response

Example

No response

[vkouk]

Summary

Hello all,

As title says I am trying to make a non-buildable lib that will hold all of my enums, interfaces etc in separate libs all of them. These will be reused to my monorepo for nestjs and angular 19 separately.

Now my question is, will this work or shall i mark them buildable like the rest of my libs?

This is my package json of my enums

{

    "name": "@repo-common/enums",

    "version": "0.0.0",

    "private": true,

    "license": "MIT",

    "main": "./src/index.ts",

    "scripts": {

        "lint": "eslint  --max-warnings 0",

        "check-types": "tsc --noEmit"

    },

    "publishConfig": {

        "access": "public"

    },

    "exports": {

        ".": "./src/index.ts"

    },

    "dependencies": {},

    "devDependencies": {}

}

This is my src/index.ts

export * from "./client";

This is my client/index.ts

export * from "./client-options.enum";

And this is my enum

export enum ClientOptions {

    IsChain = 0

}

On the other side of my nestjs app I am just using it as console.log

 console.log(

      {sChain: ClientOptions.IsChain }

Will this work or it must be buildable? Currently I get this error

Error [ERR_UNSUPPORTED_DIR_IMPORT]: Directory import '/clean/packages/enums/src/client' is not supported resolving ES modules imported from /clean/packages/enums/src/index.ts

Thanks a lot

Additional information

No response

Example

No response

Ok I think I know why it doesn't work. Because based on docs I need to have a direct mapping over here. (Which makes sense)

Otherwise I could make it buildable and have something like

exports: {
types: src/index.ts
default: dist/index.js
}

So I would use the same export path like @repo/enums but compile it to JS instead.

[vkouk]

Is there any suggestion / solution here?

[vkouk]

@anthonyshew Sorry for the direct mention but i was checkin your last video: https://www.youtube.com/watch?v=gpWDZir8dAA

I am trying to do something similar, although for nestjs i noticed this is not applicable due to different tsconfig configuration in general. Is there any workaround / alternative here?