Path: csiph.com!weretis.net!feeder7.news.weretis.net!news.mb-net.net!open-news-network.org!.POSTED.251.225.197.178.dynamic.wless.zhbmb00p-cgnat.res.cust.swisscom.ch!not-for-mail From: Thomas 'PointedEars' Lahn Newsgroups: comp.lang.javascript Subject: Re: 3rd party scripts Date: Tue, 28 Jul 2020 18:25:57 +0200 Organization: PointedEars Software (PES) Lines: 53 Message-ID: <3062290.aeNJFYEL58@PointedEars.de> References: Reply-To: Thomas 'PointedEars' Lahn Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7Bit Injection-Info: gwaiyur.mb-net.net; posting-host="251.225.197.178.dynamic.wless.zhbmb00p-cgnat.res.cust.swisscom.ch:178.197.225.251"; logging-data="27663"; mail-complaints-to="abuse@open-news-network.org" User-Agent: KNode/4.14.10 Cancel-Lock: sha1:/mtXuWfQCcHxNAyZIBPgfYk/EEg= X-User-ID: U2FsdGVkX192SjXg14bXylaxewqbXDESFWdmLwWkJRmt9rD/Qhzf9g== X-Face: %i>XG-yXR'\"2P/C_aO%~;2o~?g0pPKmbOw^=NT`tprDEf++D.m7"}HW6.#=U:?2GGctkL,f89@H46O$ASoW&?s}.k+&. I have a website that uses 3rd party code (anime.js, driver.js...) The > site works as expected but I have to manually check the 3rd party > sources to see if there are any updates. > > Then if there is an update I have to check what it is, download it, and > then test the website with it. > > Is this the nature of using 3rd party code or is there some "automated" > way to handle it? The way this works now *protects* you because your code may become incompatible to the third-party code if it is updated. In theory, there is semantic versioning, with which developers can make updates to their code and indicate that the new version only fixes bugs or introduces new features, but does not break any existing code: - A change from version 1.4.21 to 1.4.22 would indicate that only bugs were fixed. - A change from version 1.4.21 to 1.5.3 would indicate that new features were introduced in a backwards-compatible way, and some bugs were fixed. - A change from version 1.4.21 to 2.0.2 would indicate that breaking changes have been introduced, and that old code would probably have to be updated before it can be used with the new version Then it would be possible to refer to a major version and always use the newest version of the library, e.g. https://example.com/lib-1.js This could be equivalent (by server-side redirect) to https://example.com/lib-1.4.22.js if the most recent version of the 1.x series is 1.4.22. This would be similar to how GNU/Linux handles C dynamically linked library references. (A symlink to the newest/preferred version of the library is created.) But not all developers know about or observe semantic versioning, so unless the developers of your third-party library do, you have to find a way to keep yourself up to date. One possibility is to subscribe to a newsletter, code repository, or social media site of the library, if there is one. -- PointedEars FAQ: | | Twitter: @PointedEars2 | Please do not cc me./Bitte keine Kopien per E-Mail.