| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
|
|
| |
- Use yarn-berry instead of npm, with Zero Install feature and goodies
- Add `initializeToken` to post unique token to logs on startup
- Package upgrades
- Fix index.html.template tests
I will never do this again
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
Even more refactoring - however there were some small
troubles using path in the nested scripts/files, so referencing
them via the index should be a bit more stable. Plus, the config
unit tests won't just exit because of configOrError constants
strewn about the file.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
async init function. This brings more logic "to light", so it should
probably have unit tests added to check the edge cases. As a bonus, no
async runs as a result of route initialization.
Speaking of routes, it might be nice to trim down the route calls
themselves with async functions, if possible. The upload routes in
particular use a lot of async. Just a note for the future.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Wrote a couple of initial unit tests for some of the logic-heavy points
in the application, being logger.ts and formats.ts. Evidently colorize()
causes an error when transforming on the Format object that's returned.
Since that is specific to the Console transport anyways, I just moved it
to the transport, since the unit test was only testing the passed label
in the returned Formats object.
Also the bash template has some issues that I didn't test (oops), so
those are fixed now.
|
| | |
|
| | |
|
| |
|
