Hashtag

#JSR

35 posts tagged with this hashtag.

@hongminhee@hollo.social

Every time I try to publish a package to (JavaScript Registry), it frequently gets stuck in the “processing” state, so I'm seriously considering whether I should stop publishing my TypeScript packages there altogether. 🤔

A screenshot of the JSR (JavaScript Registry) publishing interface, illustrating frequent stalls in the package upload process. The list shows seven publishing attempts for pre-release versions of a package labeled “1.9.0.” Four of these attempts are indefinitely stuck in a “processing” state, with statuses showing they have been processing for periods ranging from 40 minutes to 3 weeks. In contrast, two other versions are marked as successfully published with a green checkmark, but the overall image highlights the unreliability of the publishing workflow.
ALT text

A screenshot of the JSR (JavaScript Registry) publishing interface, illustrating frequent stalls in the package upload process. The list shows seven publishing attempts for pre-release versions of a package labeled “1.9.0.” Four of these attempts are indefinitely stuck in a “processing” state, with statuses showing they have been processing for periods ranging from 40 minutes to 3 weeks. In contrast, two other versions are marked as successfully published with a green checkmark, but the overall image highlights the unreliability of the publishing workflow.

@hongminhee@hollo.social

Every time I try to publish a package to (JavaScript Registry), it frequently gets stuck in the “processing” state, so I'm seriously considering whether I should stop publishing my TypeScript packages there altogether. 🤔

A screenshot of the JSR (JavaScript Registry) publishing interface, illustrating frequent stalls in the package upload process. The list shows seven publishing attempts for pre-release versions of a package labeled “1.9.0.” Four of these attempts are indefinitely stuck in a “processing” state, with statuses showing they have been processing for periods ranging from 40 minutes to 3 weeks. In contrast, two other versions are marked as successfully published with a green checkmark, but the overall image highlights the unreliability of the publishing workflow.
ALT text

A screenshot of the JSR (JavaScript Registry) publishing interface, illustrating frequent stalls in the package upload process. The list shows seven publishing attempts for pre-release versions of a package labeled “1.9.0.” Four of these attempts are indefinitely stuck in a “processing” state, with statuses showing they have been processing for periods ranging from 40 minutes to 3 weeks. In contrast, two other versions are marked as successfully published with a green checkmark, but the overall image highlights the unreliability of the publishing workflow.

@hongminhee@hollo.social

Every time I try to publish a package to (JavaScript Registry), it frequently gets stuck in the “processing” state, so I'm seriously considering whether I should stop publishing my TypeScript packages there altogether. 🤔

A screenshot of the JSR (JavaScript Registry) publishing interface, illustrating frequent stalls in the package upload process. The list shows seven publishing attempts for pre-release versions of a package labeled “1.9.0.” Four of these attempts are indefinitely stuck in a “processing” state, with statuses showing they have been processing for periods ranging from 40 minutes to 3 weeks. In contrast, two other versions are marked as successfully published with a green checkmark, but the overall image highlights the unreliability of the publishing workflow.
ALT text

A screenshot of the JSR (JavaScript Registry) publishing interface, illustrating frequent stalls in the package upload process. The list shows seven publishing attempts for pre-release versions of a package labeled “1.9.0.” Four of these attempts are indefinitely stuck in a “processing” state, with statuses showing they have been processing for periods ranging from 40 minutes to 3 weeks. In contrast, two other versions are marked as successfully published with a green checkmark, but the overall image highlights the unreliability of the publishing workflow.

@hongminhee@hollo.social

Every time I try to publish a package to (JavaScript Registry), it frequently gets stuck in the “processing” state, so I'm seriously considering whether I should stop publishing my TypeScript packages there altogether. 🤔

A screenshot of the JSR (JavaScript Registry) publishing interface, illustrating frequent stalls in the package upload process. The list shows seven publishing attempts for pre-release versions of a package labeled “1.9.0.” Four of these attempts are indefinitely stuck in a “processing” state, with statuses showing they have been processing for periods ranging from 40 minutes to 3 weeks. In contrast, two other versions are marked as successfully published with a green checkmark, but the overall image highlights the unreliability of the publishing workflow.
ALT text

A screenshot of the JSR (JavaScript Registry) publishing interface, illustrating frequent stalls in the package upload process. The list shows seven publishing attempts for pre-release versions of a package labeled “1.9.0.” Four of these attempts are indefinitely stuck in a “processing” state, with statuses showing they have been processing for periods ranging from 40 minutes to 3 weeks. In contrast, two other versions are marked as successfully published with a green checkmark, but the overall image highlights the unreliability of the publishing workflow.

@hongminhee@hollo.social

Introducing !

A simple, cross-runtime email library that works seamlessly on , .js, , and edge functions. Zero dependencies, unified API, and excellent testability with built-in mock transport.

Switch between , , without changing your code. Available on & !

https://upyo.org/

upyo.org

Upyo

A simple and cross-runtime library for sending email messages using SMTP and various email providers

@hongminhee@hollo.social

Introducing !

A simple, cross-runtime email library that works seamlessly on , .js, , and edge functions. Zero dependencies, unified API, and excellent testability with built-in mock transport.

Switch between , , without changing your code. Available on & !

https://upyo.org/

upyo.org

Upyo

A simple and cross-runtime library for sending email messages using SMTP and various email providers

@hongminhee@hollo.social

Introducing !

A simple, cross-runtime email library that works seamlessly on , .js, , and edge functions. Zero dependencies, unified API, and excellent testability with built-in mock transport.

Switch between , , without changing your code. Available on & !

https://upyo.org/

upyo.org

Upyo

A simple and cross-runtime library for sending email messages using SMTP and various email providers

@hongminhee@hollo.social

Introducing !

A simple, cross-runtime email library that works seamlessly on , .js, , and edge functions. Zero dependencies, unified API, and excellent testability with built-in mock transport.

Switch between , , without changing your code. Available on & !

https://upyo.org/

upyo.org

Upyo

A simple and cross-runtime library for sending email messages using SMTP and various email providers

@hongminhee@hollo.social

Introducing !

A simple, cross-runtime email library that works seamlessly on , .js, , and edge functions. Zero dependencies, unified API, and excellent testability with built-in mock transport.

Switch between , , without changing your code. Available on & !

https://upyo.org/

upyo.org

Upyo

A simple and cross-runtime library for sending email messages using SMTP and various email providers

@hongminhee@hollo.social

Introducing !

A simple, cross-runtime email library that works seamlessly on , .js, , and edge functions. Zero dependencies, unified API, and excellent testability with built-in mock transport.

Switch between , , without changing your code. Available on & !

https://upyo.org/

upyo.org

Upyo

A simple and cross-runtime library for sending email messages using SMTP and various email providers

@hongminhee@hollo.social

Introducing !

A simple, cross-runtime email library that works seamlessly on , .js, , and edge functions. Zero dependencies, unified API, and excellent testability with built-in mock transport.

Switch between , , without changing your code. Available on & !

https://upyo.org/

upyo.org

Upyo

A simple and cross-runtime library for sending email messages using SMTP and various email providers

@hongminhee@hollo.social

Introducing !

A simple, cross-runtime email library that works seamlessly on , .js, , and edge functions. Zero dependencies, unified API, and excellent testability with built-in mock transport.

Switch between , , without changing your code. Available on & !

https://upyo.org/

upyo.org

Upyo

A simple and cross-runtime library for sending email messages using SMTP and various email providers

@hongminhee@hollo.social

Introducing !

A simple, cross-runtime email library that works seamlessly on , .js, , and edge functions. Zero dependencies, unified API, and excellent testability with built-in mock transport.

Switch between , , without changing your code. Available on & !

https://upyo.org/

upyo.org

Upyo

A simple and cross-runtime library for sending email messages using SMTP and various email providers

@hongminhee@hollo.social

Introducing !

A simple, cross-runtime email library that works seamlessly on , .js, , and edge functions. Zero dependencies, unified API, and excellent testability with built-in mock transport.

Switch between , , without changing your code. Available on & !

https://upyo.org/

upyo.org

Upyo

A simple and cross-runtime library for sending email messages using SMTP and various email providers

@hongminhee@hollo.social

Introducing !

A simple, cross-runtime email library that works seamlessly on , .js, , and edge functions. Zero dependencies, unified API, and excellent testability with built-in mock transport.

Switch between , , without changing your code. Available on & !

https://upyo.org/

upyo.org

Upyo

A simple and cross-runtime library for sending email messages using SMTP and various email providers

@hongminhee@hollo.social

Introducing !

A simple, cross-runtime email library that works seamlessly on , .js, , and edge functions. Zero dependencies, unified API, and excellent testability with built-in mock transport.

Switch between , , without changing your code. Available on & !

https://upyo.org/

upyo.org

Upyo

A simple and cross-runtime library for sending email messages using SMTP and various email providers

@zeab@fosstodon.org · Reply to Alejandro Baez

I'm definitely having fun hacking away at . 😄

Right now, getting used to using the import. Which can effectively pull almost any js module. And with being a thing... let's just say silverbullet instance is going to get weird. 😅

I'm honestly surprised it took this log to learn of this gem. Likely due to my still very much liking . Although... give me a few weeks... I'll likely build my own journaling system on this thing. 😇

silverbullet.md/API/js

silverbullet.md

API/js

API docs for Space Lua's js module, which provides JavaScript interoperability. js.import(url)Imports a JavaScript module from a URL. Returns the imported module.Example:-- Import lodash librarylocal lodashLib = js.import("https://esm.sh/lodash@4.17.

@zeab@fosstodon.org · Reply to Alejandro Baez

I'm definitely having fun hacking away at . 😄

Right now, getting used to using the import. Which can effectively pull almost any js module. And with being a thing... let's just say silverbullet instance is going to get weird. 😅

I'm honestly surprised it took this log to learn of this gem. Likely due to my still very much liking . Although... give me a few weeks... I'll likely build my own journaling system on this thing. 😇

silverbullet.md/API/js

silverbullet.md

API/js

API docs for Space Lua's js module, which provides JavaScript interoperability. js.import(url)Imports a JavaScript module from a URL. Returns the imported module.Example:-- Import lodash librarylocal lodashLib = js.import("https://esm.sh/lodash@4.17.

@phocks@bne.social

Thought it might be fun to make a small jsr package that actually has a bit of real-world utility. So here's `isit` as in `isit("Friday") ? "Hooray!" : "Boo!"` which I'll use in our morning work standup bot to send a different Teams meeting link depending on what day it is. Maybe it'll be useful to someone else too. It supports custom Dates and timezone offsets too. Enjoy! jsr.io/@phocks/isit

@noim@noc.social · Reply to noim

The requirements are:
- needs to work offline in
- user scripts can load additional dependencies, that also need to work offline the next launch
- user can access script dir and write scripts with vscode. Version of reactive-home needs to match the current docker image version
- should be available on

I have an idea of how I can achieve this, but it is annoying to refactor and test because, at the end of the day, it needs to work again since it powers my haha