use eslint-plugin-n/no-unsupported-features rules to error out the
remaining es2020 features not available for node >=12.22.0
said rules do not yet have support for es2021/es2022
db is now initiated via utilsController, and gets re-used by main
lolisafe.js script and the other controllers
this should now make sure we only have 1 active db connection pool ever
this is a pretty big refactor due to how we used to reference db,
but it should functionally be identical
turns out this fork can already proceed as-is into knex v2
WARNING: for those that fork this project and do anything significant
with database handling, please consult the following upgrade notice:
https://github.com/knex/knex/blob/master/UPGRADING.md
to see if your changes will be affected or not
** make sure to start with 0.95.0+ upgrade notice **
this requires locally linking your globally-installed sass-embedded
package, either through yarn link or whichever else
we are not requiring it explicitly because supposedly the binaries
are not widely available through all platforms
e.g.
yarn global add sass-embedded
cd ~/.config/yarn/global/node_modules/sass-embedded
yarn link
cd /path/to/this/project
yarn link sass-embedded
actually symlinking via generic ln -s would do too, but the method above
allows you to yarn link it into other projects, while maintaining
the package itself via yarn global (to update, etc.)
forcefully setting it to WebAudio seemingly disable progress bar on my
Firefox Desktop for some reason
perhaps it actually disabled the fallback mechanism
every now and then i got curious of what people add to their forks,
and sometimes i'd be like, "hey, that makes sense!"
i remember that back in the days, i switched to nunjucks because of
someone's fork too
we used to use handlebars, which i've had some misgivings with for
awhile back then
either way all i'm saying is that it's the case this time around with
this commit
thanks for reading
49d12004e8
this should properly dispose of unfinished write & hasher streams on
any errors if they have been initiated
also do content-length header check a bit more early
first layer is via sending HEAD request to the url to determine its size
via content-length header
however not all hosts properly set the header, so we ignore it if
it isn't a valid number
next via size option in fetch(), which supposedly limits response body
size during the request itself (?)
lastly via checking actual bytes written to physical file as reported by
fs.createWriteStream()
