completecoding / serverless-auto-swagger

79 stars 48 forks source link

Not working with ESM #110

Open Vaibhavriju opened 1 year ago

Vaibhavriju commented 1 year ago

I use ESM rather than CSJ. I get an error saying, "

{"errorMessage":"exports is not defined in ES module scope\nThis file is being treated as an ES module because it has a '.js' file extension and 'C:\Users\vaibh\slsapis\iot\package.json' contains \"type\": \"module\". To treat it as a CommonJS script, rename it to use the '.cjs' file extension.","errorType":"ReferenceError","stackTrace":["ReferenceError: exports is not defined in ES module scope","This file is being treated as an ES module because it has a '.js' file extension and 'C:\Users\vaibh\slsapis\iot\package.json' contains \"type\": \"module\". To treat it as a CommonJS script, rename it to use the '.cjs' file extension.","at file:///C:/Users/vaibh/slsapis/iot/swagger/swagger-html.js:2:1"]}

"

kajalj3098 commented 1 year ago

there is way around but it is not a solution because you have to keep generateSwaggerOnDeploy: false

serverless-auto-swagger creates a folder named swagger in your repo where you can update the swagger-html.js file as per your requirement but as soon as it will get generateSwaggerOnDeploy true it will update the swagger back to build setting defined in auto-swagger package.