search

postmanlabs / openapi-to-postman

Plugin for converting OpenAPI 3.0 specs to the Postman Collection (v2) format
Apache License 2.0
922 stars 199 forks source link

Issues when using pkg with openapi-to-postman #774

Closed apexkode closed 9 months ago

apexkode commented 11 months ago

Hi There I was wondering if you could help me with an issue I am seeing when trying to build openapi-to-postman with the pkg command.

After cloning the repo, I run npm install in the openapi-to-postman directory. Then I use: pkg . to create the binary.

the binary gets created and I can interact with it:

$ ./openapi-to-postmanv2-linux
    Converts a given OPENAPI specification to POSTMAN Collections v2.1.0

    Examples:
                Read spec.yaml or spec.json and store the output in output.json after conversion
                   ./openapi2postmanv2 -s spec.yaml -o output.json

                Read spec.yaml or spec.json and print the output to the Console
                   ./openapi2postmanv2 -s spec.yaml

                Read spec.yaml or spec.json and print the prettified output to the Console
                  ./openapi2postmanv2 -s spec.yaml -p

$ ./openapi-to-postmanv2-linux  --version
4.18.0

However during the pkg command running a lot of warnings are created:

> pkg@5.8.1
> Targets not specified. Assuming:
  node14-linux-x64, node14-macos-x64, node14-win-x64
> Warning Cannot find module '_process' from '/home/build/tmp/openapi-to-postman/assets'  in /home/build/tmp/openapi-to-postman/assets/json-schema-faker.js
> Warning Cannot find module './dict' from '/home/build/tmp/openapi-to-postman/assets'  in /home/build/tmp/openapi-to-postman/assets/json-schema-faker.js
> Warning Cannot find module './aesprim' from '/home/build/tmp/openapi-to-postman/assets'  in /home/build/tmp/openapi-to-postman/assets/json-schema-faker.js
> Warning Cannot find module './slice' from '/home/build/tmp/openapi-to-postman/assets'  in /home/build/tmp/openapi-to-postman/assets/json-schema-faker.js
...
... omitted lots of similar lines
...

Are these warnings safe to ignore, or do I need to do some extra setup in order to get rid of them?

VShingala commented 9 months ago

@apexkode These warnings can be ignored since they do not affect the output in any form. These warnings are due to one of third party module used as static asset in the repo named json-schema-faker.