AsyncAPI Generate Not Working Behind Node Proxy Registry about generator HOT 3 CLOSED

Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

from generator.

Killercode is an external service that is out of our control. We are not aware of any workaround 😞 only one I see is building code docker container, but this one would also have to be downloaded through proxy + it would make a learning experience "custom" and not the best.

Closing for now, and if you have an idea how that could be fixed, please let us know

from generator.

@derberg. I followed the tutorial steps in my working station without any docker container.
My working station runs behind a node registry proxy.
I was wondering if the async cli has some parameter that would allow me to avoid

$ asyncapi generate fromTemplate asyncapi.yaml @asyncapi/[email protected] -o output -p server=mosquitto
Generation in progress. Keep calm and wait a bit... done

Generator Error: request to https://registry.npmjs.org/@asyncapi%2fgenerator-react-sdk failed, reason: self-signed certificate in certificate chain``

My current npm works behind a proxy. I tried to set it global but it is still hitting that endpoint.
Is there a way to pass a parameter to the cli to force the npm registry?

from generator.