Egregoros

jquery 4.0.0 has been released https://blog.jquery.com/2026/01/17/jquery-4-0-0/

@lain tfw still on 1.x (never update

@hakui @lain jquery 1 has some vulnerabilities

@meowski @lain i know

@hakui @lain keeps things interesting

@meowski @lain it's like replacing the plumbing in a 19th century house

you know it has to be done but the effort it takes just makes you want to put it off until Maybe Later (i.e. never

@hakui @lain jquery updates tend to be fairly painless iirc

@meowski @lain what's the process like

>run jquery-migrate
>get a list of functions to rewrite because they're deprecated
>rewrite those parts and link the new version

?

@hakui @lain i've only just dropped in the new one and never had to deal with deprecation. but i guess that would be a safer way. i think not much has been deprecated over the years

@meowski @lain note that my codebase is 1.x and ideally we want it to go up to 3

@hakui @lain well you have a dev host right just roll it out there and test it 😏

@meowski @lain >well you have a dev host right
mpv-shot0087.jpg

@hakui @lain it's straightforward with most modern web frameworks to clone a site on a subdomain like dev.example.com or mysite.local on your local workstation. even wordpress that litters the db with hard-coded domain names you can clone it and just find and replace all the instances of it, change a few config variables and it works*

* some WP plugins cause annoyances worse like wordfence

@meowski @lain it's multiple 15+ year old ASP.NET web apps with more duct tape than actual code

@hakui @lain welp

@meowski @lain as i said, 19th century buildings

@hakui @lain really as long as you can perform full text searches on the db and file system it should still be doable, and since it's on a separate host it doesn't matter if it breaks. does it have binary data stores or something that would make this infeasible?

@meowski @lain >full text searches on the db
we're talking about jquery here?

i mean, like the <script> tags are all over the place in several dozen .asp files and that's all

@hakui @lain i mean for purposes of cloning the site(s) onto a dev host first, by finding all occurrences of example.com that are hard coded that would prevent this from working.

after that you just swap out jquery and see what breaks

@meowski @lain >after that you just swap out jquery and see what breaks
well that's the part i dread doing

@hakui @lain do it in dev not production, then it doesn't matter. to me this is well worth the effort to maintain dev sites for a number of other reasons as well like showing changes to the client in advance