Doug Midgley
Doug Midgley
Hey @azlam-abdulsalam, also my understanding. In this case, we could for example, just ignore the error with a warning and continue without stopping the install of other dependencies, but happy...
Indeed, most affected aspects are managed packages (think Salesforce Maps or FSL). As mentioned, a more graceful error handling could work, even it essentially still ignored specific packages
@azlam-abdulsalam when you say "resolved" - is it something we can use?
This issue is also affecting us v 4.2.11. Any guidance on that @Caitlyn-Mills?
Also facing the issue when linking a plugin :(
@AllanOricil Its a custom plugin (not published as is private, so its not installing, but linking) below is the the sample. Note: the plugin works perfectly fine, just with this...
Same thing for us. Any timelines on having this fixed/workaround being provided which doesnt stop us from upgrading. There is a couple of things which are not working in new...
Any Updates on this?
Will need to be a major release as this would break anything using commonjs referencing our project. Can be a major release JUST for this, but still needs a major....
Would be good to understand how you expect to handle this? Currently a 429 will return a 429 error which should have error code "too many requests" so i think...