![]() ![]() ![]() attr(), you give two arguments to change the data: $(".class").data("attribute", "value") Hosting internally via Bubble is always an option, and is extremely attractive for plugin dev’s when the library is pretty stable and well established and doesn’t need too many bug fixes, but sometimes CDNs do have their advantages.Just like. I think my overall point was just that if OP’s concern is with external services, there’s no difference between one CDN over another solely in terms of being an external service that can go down at any time and it 100% beyond Bubble’s control some are better than others, and some are good now but can deteriorate later. I also agree that most of the time, a library developer will minify and compile the package into a single file for the plugin dev, but I’ve had to deal with instances of that not being the case when trying to build a plugin for bubble and need to use something like browserify or webpack to compile into a single file. I totally agree with you, I didn’t mean to say that not choosing a static version is a best practice, nor do I engage in it myself, I was just listing some of the reasons why CDNs are useful. And it will also reduce nincompoops like me from throwing our hands up blaming Bubble for things out of their control, which I can only assume is a bit annoying, but could also tarnish Bubble’s image of reliability. I would very much like to see this, if it will free up bubble dev resources not having to track down issues in their eco system stemming from external problems that could be avoided. From what I understand unpkg is also no longer actively supported, and known to have reliability issues. So for what it’s worth, if you are a plug in dev, it might behove you to consider unpkg alternatives, since it may or may not become part of Bubble’s approval process in the future. I asked if Bubble had considered enforcing uploading dependencies and/or using an actively supported service like jsdelivr as part of the plug-in approval process.Īnd the answer was that yes, that has very much been part of internal discussions and this little episode has re-ignited that conversation. Instead I’ll add the opinion of a Bubble rep that is far more knowledgeable about this than me. Other nocode platforms handle the plugin development much better and don’t have this kind of problem at all.Īlthough I find this conversation fascinating, it is so far over my head that I won’t even begin to have an opinion. It avoids to load the same dependencies many times because the same file loaded in bubble’s CDN with 2 plugins will have different urls. I can see it’s useful to use an external CDN if you have the same dependencies on multiple plugins that can be used toghether in the same app. ![]() Personally I prefer to do the work and host all the dependencies in bubble to reduce the exposed surface of the app and potential points of failure. Using an external CDN is a legitimate choice. It’s the plugin’s consumer responsibility to check if a new version is published, update, test that the app is working properly and then publish the updated app. Dependencies needs updates and it is the plugin’s author responsibility to do that, test that everything is working and then publish an update. there is no free lunch: software requires maintenance.most of the time you don’t need to build the library, it’s already distributed in its bundled version.You can choose to explicitly point unpkg to a specific file, otherwise it will follow the normal conventions. Unpkg automatically tries to published the library based on instructions in the package.json. most of the libraries do not choose to publiah on unpkg too.If it’s a major update or the mantainer doesn’t follow semantic versioning you can load a version with breaking changes and your plugin will stop working without any notice blindly load the latest library is bad practice, it “should” be ok if the library follows semver and the latest update is a patch or minor update.UNPKG allows content to always use the latest version ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |