Comments (2)
I'm having this issue as well in my ESM output service.
The issue is with non-literal types like objects and enum, those are translated to a dynamic import by the plugin
then the replaceImportPath
function explicitly replace import("somepath")
to require("somepath")
swagger/lib/plugin/utils/plugin-utils.ts
Line 160 in 29f59e9
swagger/lib/plugin/utils/plugin-utils.ts
Line 207 in 29f59e9
I tried to remove those two lines and it runs perfectly fine. So technically it is not blocked by the "ESM support" issue, just making it not do the string replace if the target is ESM
from swagger.
I found this package to do monkey patch on the build, not sure how to integrate it to the cli with watch mode capability
It references microsoft/TypeScript#43329 when mentioning this "require" import issue
I guess at some point TS only emit require
for both ESM and CJS build, but now it is fixed, import/require is chosen based on the config
I guess for some reason the maintainer wanna keep existing behaviour and blindly replace it back to require
Maybe the original author can help @kamilmysliwiec
from swagger.
Related Issues (20)
- Monorepo support for the Swagger module HOT 1
- File upload only displays the string "string($binary)" instead of upload button HOT 1
- circular dependency has been detected with swagger plugin HOT 2
- Oauth2 Redirect url not working correctly without trailing path HOT 1
- The fields of DTO do not appear in Swagger UI when using CLI. HOT 1
- Wrong swagger generation for @Query with array of objects HOT 4
- Swagger is not showing extended properties HOT 7
- Custom `type` is not retained as type, but rewritten as `allOf: - $ref: ...` breaking `nullable: true` spec in `@ApiProperty` HOT 8
- Setting the name attribute results in a schema change HOT 2
- CLI Plugin cannot generate descriptions for endpoint HOT 1
- OpenAPI: Use oneOf with $ref
- Typescript Program is undefined when ts-jest isolatedModule is true
- Metadata gets incorrectly applied/merged when using loadPluginMetadata HOT 3
- Support for Header Versioning
- swagger debugging does not work properly when using @body("user") user:User as an argument, there is no Request body, but @body() user:User works fine with no argument HOT 1
- Issues with typescript >= 5.5 HOT 1
- default @ApiTag to controller name HOT 2
- Help: Need to add basic authentication to access swagger url in fastify nestjs application HOT 2
- Using Types with the metadata generator plugin doesn't seem to work HOT 1
- OpenAPI 2 fork HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from swagger.