Since the legacy config is being deprecated at the end of 2024, we
should start moving to the eslint flat config.
I avoided the tseslint config helper function so we avoid wrapping
magic.
This seems to have triggered more checking since any checks in svelte
files have appeared and the $$Generic type that is being deprecated had
to be rewritten.
Also fixes some any types that weren't caught previously
The execa update allows us two simplify two things
1. Output collection in a log file with a prefix can be done through
`stdout` and `stderr` options of `execa`.
2. We don’t need to ensure that all subprocesses are killed when the
main process exits. `execa` takes care of this
We have a new apiVersion value in the config json that needs to be
changed for each breaking change on httpd so we can simulate a new
resource to the cache and get it cleared.
Also improves the ResponseParseError giving the user more information
on, if the node or the web client is outdated
Since we don't have or want any deployments on IPFS, and we don't have
much use for hash routing else, we can clean up some code and remove
some tests.
Instead of relying on the `exit-hook` dependency, we should listen to
`exit`, `SIGINT`, `SIGTERM` and other exceptions, and kill all running
processes.
Updates transitive dependencies
Fixes zod vulnerability
> Zod version 3.22.2 allows an attacker to perform a denial of service while validating emails.
Signed-off-by: Sebastian Martinez <me@sebastinez.dev>
This fixes the issue with rendering code blocks without a blank line
between text and the start of a codeblock that starts with a `$`
Signed-off-by: Sebastian Martinez <me@sebastinez.dev>
- prettier assumes now that we want to ignore files listed in .gitignore
by default
- trailingComma: all is now the default value
Signed-off-by: Sebastian Martinez <me@sebastinez.dev>
Based on a new addition to marked, this commits replaces the imported
marked namespaces with a Marked class, that doesn't change when
`marked.use` introduces new options or extensions.
Also changes the naming slighty to use `markdown` as module, so it
sounds more generic.
Reference: https://github.com/markedjs/marked/pull/2831
Signed-off-by: Sebastian Martinez <me@sebastinez.dev>
* We remove all styling related lints and use `eslint-config-prettier`.
There’s no need to bother developers with styling lints because
Prettier already takes care of that. (This is the [recommended
integration with Prettier][1])
* We use the “warning” level for lints that are code style related. This
allows developers to distinguish issues that need to be fixed now
(like type errors) and issues that can be fixed later (like style
errors). We do enforce all lints on CI by settings
`--max-warnings=0`.
[1]: https://prettier.io/docs/en/integrating-with-linters.html
Signed-off-by: Thomas Scholtes <geigerzaehler@axiom.fm>
Sebastian Martinez