mirror of
https://github.com/ArchiveBox/ArchiveBox.git
synced 2026-04-25 17:16:00 +03:00
[GH-ISSUE #1220] Feature Request: Update singlefile to latest version (PR available) #3769
Labels
No labels
expected: maybe someday
expected: next release
expected: release after next
expected: unlikely unless contributed
good first ticket
help wanted
pull-request
scope: all users
scope: windows users
size: easy
size: hard
size: medium
size: medium
status: backlog
status: blocked
status: done
status: idea-phase
status: needs followup
status: wip
status: wontfix
touches: API/CLI/Spec
touches: configuration
touches: data/schema/architecture
touches: dependencies/packaging
touches: docs
touches: js
touches: views/replayers/html/css
why: correctness
why: functionality
why: performance
why: security
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ArchiveBox#3769
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @spresse1 on GitHub (Aug 29, 2023).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/1220
Type
What is the problem that your feature request solves
The version of SingleFile currently pulled into ArchiveBox is from 2021 and pinned to a specific git commit. SingleFile has since split into the SingleFile browser plugin and single-file-cli and gone to version 1.
Describe the ideal specific solution you'd want, and whether it fits into any broader scope of changes
I've prepared a patch which updates NPM dependencies to pull in
single-file-cliwith the latest release. In testing using my own docker container, this was a drop-in replacement. I've used it to archive just under 500 pages at this point (importing from pinboard).I'll open a PR with the patch just as soon as I'm done with this bug report. It's unfortunately a rewrite of the NPM dependency files, but brings many things more up to date.
What hacks or alternative solutions have you tried to solve the problem?
None, wrote the fix.
How badly do you want this new feature?
@spresse1 commented on GitHub (Aug 29, 2023):
One question: I don't see an automated way of getting the latest NPM updates into package-lock.json (but do not regularly develop using NPM). Is the intent that this is done manually?
@pirate commented on GitHub (Aug 30, 2023):
Yes, because archival software has slightly different design goals than most software, I don't want to bump dependencies too frequently, lest we create a giant file of archivebox versions that need to be stored for future replaying.