azu
Duplicate of - https://github.com/oven-sh/bun/issues/4981 - https://github.com/oven-sh/bun/issues/5024
why? 2024年4月2日(火) 18:45 Claudio W ***@***.***>: > Closed #6501 as not > planned. > > — > Reply to this email directly, view it on GitHub > , or >...
I am concerned that many dead links are occurring due to this problem. - https://www.google.com/search?q=%22nodejs.org%2Fja%2Fdownload%2F%22 - https://www.google.com/search?q=%22nodejs.org%2Fes%2Fdownload%2F%22 - https://www.google.com/search?q=%22nodejs.org%2Fko%2Fdownload%2F%22 I think it's not just a translation problem.
> What you expect us to render then instead of a 404? The Japanese pages simply do not exist. I wrote: > If you not plan to support localization on...
Just to confirm, is the DuckDB wasm extension not affected by this vulnerability and safe to use? For example, when using the spatial extension from `@duckdb/duckdb-wasm` with a query like...
What API needed to create an LSP? I don't think it's worth it to provide a Parser API that summarizes parsers like Markdown, HTML, LaTeX, etc., with a `textlint` package....
I'm starting to understand what you're getting at. [TxtAST](https://textlint.org/docs/txtnode/) basically only has expressions that are roughly a subset of Markdown. Therefore, even if we implement syntax highlighting with [Semantic Tokens](https://microsoft.github.io/language-server-protocol/specifications/specification-3-16/#textDocument_semanticTokens)...
Perhaps an implementation of a similar idea: - [t3tra-dev/MoZuku: 日本語文章の解析・校正を行う LSP サーバー。](https://github.com/t3tra-dev/MoZuku)
@dependabot merge 6/25/2025, 12:26:22 AM "proofdict/proofdict" ***@***.***>
@dependabot merge 6/25/2025, 12:26:23 PM "proofdict/proofdict" ***@***.***>