Skypack looked like a cool new thing a few years ago. We used it in a few places with some of our scripts. It looks to be struggling as of this writing. So we used this page to find and replace our usages of Skypack with jsDelivr. Having finished that work, we leave behind this document of how it worked to inform future content migrations.
This page is a Project.
We are delighted again with ways these simple mechanisms in federated wiki can be combined ad hoc into workflows to organize maintenance over a growing body of knowledge.
We used the Grep plugin to find all the pages in this wiki with code items that mentioned skypack. Since we finished the work, this no longer finds any pages on this site. But it could still be useful to other wikis in the federation. An author of another wiki could include this page in a lineup from their own wiki to find pages mentioning skypack in code.
ITEM code TEXT skypack
See About Grep Plugin.
We used the simple federated wiki todo list workflow mostly to keep a record of our work in the journal of this page. This was slightly tedious, but tolerable given the small number of pages. We created a paragraph with just a link to each of the pages found with grep. And we created two pagefolds to group those paragraphs.
Next we visited the first page, found where skypack was referenced, searched jsDelivr for an equivalent URL for the library, replaced the import, and then tested the behavior of the widgets on that page.
To check that our work was done, we re-ran the grep above to double-check there were no other references to skypack. Once confirmed, we moved the paragraph linking to that page from our todo section to the done section.
This use of simple paragraphs to track progress made it easy to spread the cleanup into small projects over a couple days.
todo
done
.
At the time of this project, browser enforcement of separation between https and http internet prevented our exploration of site survey and probe. Some time after replacing skypack, we did port code for survey and probe. See Site Survey Factory.
For comparison, here we grep for pages in this wiki with items that mention jsDeliver.
ITEM code TEXT jsdelivr
While documenting the process we also found another way to pursue this kind of project.
.. full-text search ..
For context, we have a lot of sites where we might have written some code. How would we find needles of skypack in this larger haystack?
ROSTER wiki.dbbs.co/eric-dobbs
That turned out to be quite easy. Load the roster into our neighborhood and use built-in full-text search for skypack. It's not as specific as the grep search which limits itself to code items. But it has the advantage of looking over the whole neighborhood.
Here we can build another todo list and drag in copies of the references from the search results. We copied a couple other items from the search results for completeness: the paragraph describing the results and a reference to this page.
Turns out there are only two other pages to clean up.
todo
String 'skypack' found on 3 of 1053 pages from 17 sites. Text matched on no titles, no paragraphs, and no slugs. Elapsed time 3 milliseconds.
Skypack looked like a cool new thing a few years ago. We used it in a few places with some of our scripts. It looks to be struggling as of this writing. So we used this page to find and replace our usages of Skypack with jsDelivr. Having finished that work, we leave behind this document of how it worked to inform future content migrations.
done
Eventually we need to add the "long diagonals" 2-6&7, 5-8&9, 11-3&4, and 10-6&7. :>).
We scribble a line on a canvas from a Stream of Points.
.