Feature Request: using generated code as an artifact

[thejeff77]

Hello there,

We noticed that there was no compiled code, or build steps outlined in the generated package.json output as part of the default generated typescript client.

Our intention is to upload the results of this generation as an npm artifact to an internal npm package repository.

Typically this involves the library including a dist folder, and built code that is easily consumable from a node_modules folder

Ex in package.json:

{
  "main": "dist/index.js",
  "types": "dist/index.d.ts",
  "files": ["dist/"]
}

Do you have any guidance, or support for uploading a generated hey-api generated client as an npm artifact that we may have missed in the documentation?

Thanks for any assistance, or elaboration. Anything would help.

[mrlubos]

Hey @thejeff77! Not at the moment but I do plan to address it this year

[thejeff77]

@mrlubos

[thejeff77]

@mrlubos, curious if you have an idea when this year this might happen? We're just trying to figure out if we should roll it on our own or wait.

[mrlubos]

I was meaning to talk to you! Do you want to schedule a call for next week after Monday? I'm in GMT+8 https://calendly.com/lubos-heyapi/new-meeting