Anyone know of a good Schedular in #NodeJS? Trying to move away from agenda (https://github.com/agenda/agenda) as it's not been updated in years, and we want to use Postgres as our backing store.
Any suggestions?
Recent searches
Search options
#nodejs
18 posts18 participants5 posts today
Greg Cocks Wildlife Protection System for Train Safety
--
https://github.com/Vinonsan/Srilankan-Railway-Safety-system <-- shared GitHub repository
--
#GIS #spatial #mapping #TechForGood #WildlifeConservation #AI #MachineLearning #ObjectDetection #ReactJS #NodeJS #Innovation #Sustainability #ConservationTech #AIForConservation #srilanka #risk #hazard #safety #model #modeling #mitigation #elephant #bull #wildlife #livestock #protection #realtime #detection #weather #safety #railroad #train #transportation #infrastructure #spatialanalysis #conservation #railway #railroad #economics
@cwebber What do you think of JS packages, ten years later (same day, what a coincidence)?
dustycloud.orgLet's Package jQuery: A Javascript Packaging Dystopian Novella -- Dustycloud Brainstorms
Package Manager for Markdown
I'm working on a project that is intended to encourage folk to make markdown text files which can be bundled together in different bundles of text files using a package manager.
Question for coders; Which package manager would you suggest I use?
Main criterias (in order) are:
1. Easy for someone with basic command line skills to edit the file and update version numbers and add additional packages.
2. All being equal, more commonly and easy to setup is preferred.
#Markdown #CommonMark #PackageManager #Programming #Dev
#NPM #RubyGems #Cargo #PickingAMastodonInstance
#Ruby #Python #Rust #Javascript #NodeJs #Lisp #CommonGuide
New Kitten update
• 
Kitten HTML templates and kitten.Component render functions can now be async.
This is quite a big one and it took me finally biting the bullet and getting my head around generators in JavaScript to implement properly.
So now you can mix synchronous and asynchronous components as you like and if there are any asynchronous components in your templates they will automatically be awaited (even if you forget to use await) ;)
I’ll write a proper post/tutorial/documentation for it soon but for the time being enjoy the screenshots where a layout template gets the latest three posts from my mock fediverse public timeline service and displays them on the page.
The kitten.Component version also has a refresh button that streams a different three to the page.
For those of you unfamiliar with Kitten, this is all the code in either example. No scaffolding, nothing. Pop either into a file called index.page.js and run kitten in that folder and visit https://localhost to see the example run.
Enjoy!
![const BasicLayoutTemplate = async ({ title, SLOT }) => {
const posts = (await (await fetch('https://streamiverse.small-web.org/public/')).json()).splice(0, 3)
return kitten.html`
<main>
<page css>
<h1>${title}</h1>
${SLOT}
<h2>Fediverse posts</h2>
<ul>
${posts.map(post => kitten.html`
<li><img src='${post.account.avatar}'> ${[post.content]}</li>
`)}
</ul>
<style>
li { display: flex; gap: 1em; margin-bottom: 1em; }
img { width: 5em; height: auto; }
</style>
</main>
`
}
export default async () => await kitten.html`
<${BasicLayoutTemplate} title='Async components are fun!'>
<markdown>
Oh, isn’t this __nice?__
</markdown>
</>
`](https://s3-eu-central-1.amazonaws.com/mastodon-aral/media_attachments/files/114/258/812/670/834/838/original/228733ad125b57f4.png "const BasicLayoutTemplate = async ({ title, SLOT }) => {
const posts = (await (await fetch('https://streamiverse.small-web.org/public/')).json()).splice(0, 3)
return kitten.html`
<main>
<page css>
<h1>${title}</h1>
${SLOT}
<h2>Fediverse posts</h2>
<ul>
${posts.map(post => kitten.html`
<li><img src='${post.account.avatar}'> ${[post.content]}</li>
`)}
</ul>
<style>
li { display: flex; gap: 1em; margin-bottom: 1em; }
img { width: 5em; height: auto; }
</style>
</main>
`
}
export default async () => await kitten.html`
<${BasicLayoutTemplate} title='Async components are fun!'>
<markdown>
Oh, isn’t this __nice?__
</markdown>
</>
`")
![class BasicLayoutTemplate extends kitten.Component {
async html ({title, SLOT}) {
return kitten.html`
<main id='page' morph>
<page css>
<h1>${title}</h1>
${SLOT}
<${FediversePosts.connectedTo(this)} />
</main>
`
}
}
class FediversePosts extends kitten.Component {
async html () {
const posts = (await (await fetch('https://streamiverse.small-web.org/public/')).json()).splice(Math.floor(Math.random()*6), 3)
return kitten.html`
<div id='posts' morph>
<h2>Fediverse posts</h2>
<ul>
${posts.map(post => kitten.html`
<li><img src='${post.account.avatar}'> ${[post.content]}</li>
`)}
</ul>
<button name='refresh' connect>Refresh</button>
<style>
li { display: flex; gap: 1em; margin-bottom: 1em; }
img { width: 5em; height: auto; }
</style>
</div>
`
}
onRefresh () { this.update() }
}
export default class MyPage extends kitten.Page {
async html () {
return kitten.html`
<${BasicLayoutTemplate.connectedTo(this)} title='Async components are fun!'>
<markdown>
Oh, isn’t this __nice?__
</markdown>
</>
`
}
}](https://s3-eu-central-1.amazonaws.com/mastodon-aral/media_attachments/files/114/258/813/076/463/648/original/22f714259e01b4f8.png "class BasicLayoutTemplate extends kitten.Component {
async html ({title, SLOT}) {
return kitten.html`
<main id='page' morph>
<page css>
<h1>${title}</h1>
${SLOT}
<${FediversePosts.connectedTo(this)} />
</main>
`
}
}
class FediversePosts extends kitten.Component {
async html () {
const posts = (await (await fetch('https://streamiverse.small-web.org/public/')).json()).splice(Math.floor(Math.random()*6), 3)
return kitten.html`
<div id='posts' morph>
<h2>Fediverse posts</h2>
<ul>
${posts.map(post => kitten.html`
<li><img src='${post.account.avatar}'> ${[post.content]}</li>
`)}
</ul>
<button name='refresh' connect>Refresh</button>
<style>
li { display: flex; gap: 1em; margin-bottom: 1em; }
img { width: 5em; height: auto; }
</style>
</div>
`
}
onRefresh () { this.update() }
}
export default class MyPage extends kitten.Page {
async html () {
return kitten.html`
<${BasicLayoutTemplate.connectedTo(this)} title='Async components are fun!'>
<markdown>
Oh, isn’t this __nice?__
</markdown>
</>
`
}
}")
Looking for CMS advice
Hey Web devs!
Do you have any suggestions, tips, opinions, dos, don’ts about headless CMSes?
I have a growing list of small/mid non-profits and collectives asking for my help to (re)make their website. I totally want to help, but I don’t have much time, especially considering that they generally have little or no funding—I would most definitely point them to @VillageOneCoop, otherwise.
Therefore, I want a super simple and replicable solution where I can copy-paste most of the code, while providing them with a stable, fast, and modern solution. I had a look at the Headless CMS section in the Jamstack website, but I need opinions from people who actually used some of that software already.
Needs
- I want to code and configure everything using @eleventy
- Admin interface (#WebApp) for the client to add pages and write posts
- Static website in the front-end
- Simple and reliable CI/CD
- No/minimal maintenance after the first setup
- Self-hostable (I was taking this for granted so much that I forgot to write it)
- #OpenSource
Nice to have
- Possibly using #Deno, not #NodeJS
- Allowing the client to customize a bit their website through the admin interface, with a GUI
- CMS app packaged on @yunohost
- No CMS vendor lock-in
- I’d love to write as little JavaScript as possible
- #FreeSoftware
Absolutely not
- Front-end #JavaScript frameworks
Please, boost this and ask around! Links to videos, tutorials, and resources are welcome.
People whose perspective I would really value: @zachleat @harryfk @deno_land @jaredwhite @vanillaweb @stefan @mxbck @WeirdWriter @deadsuperhero (Sorry if I am spamming you!)
Jamstack.orgHeadless CMS - Top Content Management Systems | JamstackCheck out this showcase of some of the best, open source headless CMSes. This is community-drive so be sure to submit your favorite CMS today!
A simple #nodejs server & #htmx client to demo the new #ietf's draft on the #idempotency key #header:
https://codeberg.org/evasync/the-idempotency-key
(draft spec can be found here: https://datatracker.ietf.org/doc/draft-ietf-httpapi-idempotency-key-header/)
Codeberg.orgthe-idempotency-keyexample server/client for using idempotency keys according to the IETF spec
Replied in thread
@henry Having (almost fully) switched to #NodeJS in 2012, I quickly recognized the danger of relying to _anything_ (#npm included, this one gave me a lot of pain for several times over the years).
Ended up with a monstrous monorepo. Forked (and improved) just 2 other people's repos, one abandoned and one that took months to finally get it right regarding garbage collection, but I had no time to wait.
Thereby I never got to a situation to hate a programming language because of the hype around it, but it surely got me coding a ton of #javascript.
The experience helped me a lot in JS5=>ECMAScript and ECMAScript=>TypeScript switching in the last year or so.
Just tried to run a dev build of a #NodeJS application and apparently #bookworm is too old a development environment for modern #javascript app. Watching the list of js dependencies getting pulled in made #rust look positively svelte.
Looks as if Claude 3.7 Sonnet is of the opinion that the mock object must have all properties it can possible find in its dataset .... #funwithai #typescript #nodejs
Replied in thread
@richardlau Thanks Richard, I will respin the older Node-RED containers next week to pick up the last batch of CVE patches.
#NPM: Two malicious packages were discovered on npm (#NodeJS package manager) that covertly patch legitimate, locally installed packages to inject a persistent reverse shell backdoor:
#SoftwareSupplyChainSecurity
https://www.bleepingcomputer.com/news/security/new-npm-attack-poisons-local-packages-with-backdoors/
Nōdo – Call Node.js from Ruby
https://github.com/mtgrosser/nodo
Discussions: https://discu.eu/q/https://github.com/mtgrosser/nodo
Securing JavaScript Applications Against Common Attacks https://chat-to.dev/post?id=S2pGb2pCSEJpR0VhTHhKNXFtaGRDZz09 #javascript #reactjs #nodejs #hacking #programming
Master Python https://leanpub.com/b/masterpython by Noah Gift and Alfredo Deza is the featured bundle of ebooks 
on the Leanpub homepage! https://leanpub.com #Python #Devops #SoftwareEngineering #AutomatedSoftwareTesting #NodeJs #Ruby #Go #R #CloudComputing #books #ebooks
In #Deno `url.domainToASCII` behaves differently from #nodejs and #bun
https://blog.revathskumar.com/2025/03/deno-url-domainToASCII-behaves-differently-from-nodejs.html
blog.revathskumar.com · Deno : url.domainToASCII behaves differently from nodejsDeno : url.domainToASCII behaves differently from nodejs
»10 Gründe JavaScript zu hassen – oder zu lieben:
Drei Dekaden der Entwicklungsarbeit gehen auch an JavaScript nicht spurlos vorüber. Im Guten, wie im Schlechten.«
Ich sehe dies sehr ähnlich und bin aber immer noch der Meinung, dass JavaScript (TypeScript) eigentlich nur im Browser angewendet werden sollte da ansonsten "zu langsam" ist.
https://www.computerwoche.de/article/3844108/10-grunde-javascript-zu-hassen-oder-zu-lieben.html
Computerwoche10 Gründe JavaScript zu hassen – oder zu liebenDrei Dekaden der Entwicklungsarbeit gehen auch an JavaScript nicht spurlos vorüber. Im Guten, wie im Schlechten.