Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multiple runtime dependencies for backend frameworks. #1626

Open
JimmyBjorklund opened this issue May 13, 2024 · 0 comments
Open

Multiple runtime dependencies for backend frameworks. #1626

JimmyBjorklund opened this issue May 13, 2024 · 0 comments

Comments

@JimmyBjorklund
Copy link

The template file in the runtime library drags in all tre web backends and all their dependencies, is there a way to have this generated during code generation instead of having this input file?

packages/runtime/src/routeGeneration/templates

export * from "./templateService";
export * from "./express/expressTemplateService";
export * from "./hapi/hapiTemplateService";
export * from "./koa/koaTemplateService";

Seems strange to have to depend on all if you only are needing one at the time.

  "dependencies": {
    "@hapi/boom": "^10.0.1",
    "@hapi/hapi": "^21.3.3",
    "@types/koa": "^2.15.0",
    "@types/multer": "^1.4.11",
    "express": "^4.18.3",

Have the end user add the relevant runtime dependency in the packet.json file instead of pulling in all three for them.
/J

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant