Autorest fails to resolve csharp extension package. Looks at wrong path #5068
Labels
customer-reported
Issues that are reported by GitHub users external to the Azure organization.
question
The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Our enterprise setup artifactory and we must use that in order to get npm packages. npmrc has registry defined and I was able to install autorest package. I struggled to get core and csharp for sometime using
autorest --help --debug
. Finally I added @autorest/core and @autorest/csharp packages using npm install. It did install those extension packages in global npm cache. With that atleast I can see output forautorest --help
cli command. I thought it is all good now.But when I run autorest for client generation, I stuck with an error saying unable to resolve csharp package, though it is in npm\node_modules. If you notice the log and stack trace, there is path issue. autorest is expecting
nodemodules
folder butnode_modules
exists.I am not sure if it is a bug with package or something wrong with our enterprise setup.
I appreciate your help in showing me a direction to resolve this
input yaml file
gen.yaml
cli command
autorest gen.yaml
output
The text was updated successfully, but these errors were encountered: