2025-05-27 Trying out Defuddle an npm tool via Deno
Having access to Deno, also means having access to the npm ecosystem without having to install nodejs directly. For example, it is possible to run npm cli utilities directly from Deno. Some caveats do apply such as utilities which have a native binary / lib component might or might not work. That would depend if a FreeBSD version of the lib was also packaged npm (most likely not). However, pure js libs are fair game. For example, a tool like defuddle-cli is easily accessible from Deno. Below shows how to run it with the proper allowed permissions.
$ deno run --allow-read --allow-env --allow-net npm:defuddle-cli parse -m https://freebsdfoundation.org/blog/the-report-of-my-death-was-an-exaggeration/ | head -n 4
##### May 20, 2025
I’ve been here at The Foundation for about three months now. During that time, I’ve had a few conversations with businesses using FreeBSD, and interested in using FreeBSD. On more than one occasion, a statement has cropped up that’s made me raise my eyebrows — because it’s not something I see, or even feel. That statement is “isn’t FreeBSD dying?” Wait! What? Why would you even think that? As I’ve picked it apart, I’ve come to a startling conclusion and a very obvious fact. Before we head on this journey together, let me answer the question quickly. No, FreeBSD is not dead, or even dying. Here’s how I know for sure… In case you are curious of just what specific permissions Deno is requesting, here is a log of running this. Note it is not unusual for Deno to need access to a node_modules directory. And for network aware tools, it is also common to allow network access. Feel free to tune to your liking.
$ deno run npm:defuddle-cli parse -m https://freebsdfoundation.org/blog/the-report-of-my-death-was-an-exaggeration/ | head -n 4
┏ ⚠️ Deno requests read access to "/home/user/.cache/deno/node_modules".
┠─ To see a stack trace for this prompt, set the DENO_TRACE_PERMISSIONS environme✅ Granted read access to "/home/user/.cache/deno/node_modules".
┏ ⚠️ Deno requests read access to "/home/user/.cache/node_modules".
┠─ To see a stack trace for this prompt, set the DENO_TRACE_PERMISSIONS environme✅ Granted read access to "/home/user/.cache/node_modules".
┏ ⚠️ Deno requests read access to "/home/user/node_modules".
┠─ To see a stack trace for this prompt, set the DENO_TRACE_PERMISSIONS environme✅ Granted read access to "/home/user/node_modules".
┏ ⚠️ Deno requests read access to "/home/node_modules".
┠─ To see a stack trace for this prompt, set the DENO_TRACE_PERMISSIONS environme✅ Granted read access to "/home/node_modules".
┏ ⚠️ Deno requests read access to "/node_modules".
┠─ To see a stack trace for this prompt, set the DENO_TRACE_PERMISSIONS environme✅ Granted read access to "/node_modules".
┏ ⚠️ Deno requests env access.
┠─ To see a stack trace for this prompt, set the DENO_TRACE_PERMISSIONS environme✅ Granted env access.
┏ ⚠️ Deno requests net access to "freebsdfoundation.org:443".
┠─ Requested by `node:dns.lookup()` API.
✅ Granted net access to "freebsdfoundation.org:443".
##### May 20, 2025
I’ve been here at The Foundation for about three months now. During that time, I’ve had a few conversations with businesses using FreeBSD, and interested in using FreeBSD. On more than one occasion, a statement has cropped up that’s made me raise my eyebrows — because it’s not something I see, or even feel. That statement is “isn’t FreeBSD dying?” Wait! What? Why would you even think that? As I’ve picked it apart, I’ve come to a startling conclusion and a very obvious fact. Before we head on this journey together, let me answer the question quickly. No, FreeBSD is not dead, or even dying. Here’s how I know for sure…