You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 29, 2019. It is now read-only.
Someone must have recently added module (react-contextmenu) to cdnjs recently, because it broke my app. It used to fetch react-contextmenu/dist/react-contextmenu.js from unpkg.com but once the cdnjs version was uploaded it tried to get it from cdnjs but that path /dist/react-contextmenu.js didn't work because cdnjs doesn't copy the package folder structure like unpkg does.
Or at least I think that's what happened. Anyhoo... I really have no love for cdnjs because I find unpkg much more predictable and if you've got some spare cycles I'd love a way to just disable the cdnjs option bc it's only caused me trouble. :)
The text was updated successfully, but these errors were encountered:
I mean, obviously my app breaking is my fault - I'm not trying to make it production quality at the moment - I just mean this as feedback about what is working and what isn't for me with getlibs, and cdnjs as the default hasn't been working well for me.
The idea behind cdnjs was that the packages there were specifically made for a browser and therefore have better chances to run than average npm code which may or may not have a dist folder and 'browser' entry in package.json. Maybe this is no longer the case - can you give me more examples where cdnjs package did not do what you want?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Someone must have recently added module (react-contextmenu) to cdnjs recently, because it broke my app. It used to fetch
react-contextmenu/dist/react-contextmenu.js
from unpkg.com but once the cdnjs version was uploaded it tried to get it from cdnjs but that path /dist/react-contextmenu.js didn't work because cdnjs doesn't copy the package folder structure like unpkg does.Or at least I think that's what happened. Anyhoo... I really have no love for cdnjs because I find unpkg much more predictable and if you've got some spare cycles I'd love a way to just disable the cdnjs option bc it's only caused me trouble. :)
The text was updated successfully, but these errors were encountered: