Update Docusaurus 3 and other npm packages #282
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
this branch includes some manual updates to markdown files, where certain TypeScript documentation syntax couldn't be parsed.I addressed most of these by wrapping code in ats
code block. A dozen or so others, I tried wrapping in code syntax.It looks like the docs may have been generated using
typedoc
, and if so, it'd be worthwhile to regenerate thescrypt-ts
documentation.Update:
I ended up adding
typedoc
to this branch and can generate the latestscrypt-ts
docs usingnpx typedoc
.There appears to be a change with the BSV library, such that the latest version of
scrypt-ts
is now using@scrypt-inc/bsv
. These files were generated, but I removed them for now.They can be regenerated easily by running
npx typedoc
again.I did notice that the docs showed more
README
files in the docs, which looked a little odd, which is why I ended up deleting them for now.