
anna_lillith 🇺🇦🌱🐖
@anna_lillith@mas.to
This news is a devastating blow to conservation efforts.
@anna_lillith@mas.to
This news is a devastating blow to conservation efforts.
@kubikpixel@chaos.social
»Rust env_logger Example – Simplified Logging in Rust:
Logging is an essential part of software development, providing insight into the behavior of an application. Rust offers several logging crates, and env_logger is one of the most popular for its simplicity and flexibility«
I posted this link here so that I can find it again - certainly never in my bunch of the disordered link storage ;)
📝 https://scribe.rip/@aleksej.gudkov/rust-env-logger-example-simplified-logging-in-rust-938acbb3dbe2
#webdev #rust #logging #rustlang #dev #env #simplified #log #sec #development
@kubikpixel@chaos.social
»Rust env_logger Example – Simplified Logging in Rust:
Logging is an essential part of software development, providing insight into the behavior of an application. Rust offers several logging crates, and env_logger is one of the most popular for its simplicity and flexibility«
I posted this link here so that I can find it again - certainly never in my bunch of the disordered link storage ;)
📝 https://scribe.rip/@aleksej.gudkov/rust-env-logger-example-simplified-logging-in-rust-938acbb3dbe2
#webdev #rust #logging #rustlang #dev #env #simplified #log #sec #development
@hongminhee@hollo.social
Just released #LogTape 0.9.0! 🎉
This version brings two major improvements to our zero-dependency #logging library for #TypeScript:
New Synchronous Configuration API: You can now configure LogTape synchronously with configureSync()
, disposeSync()
, and resetSync()
. Perfect for simpler setups where you don't need async
operations!
Better Runtime Compatibility: We've moved all file-related components to a separate @logtape/file
package. This means the core package now works flawlessly across all JavaScript environments—browsers, edge functions, and various bundlers without any file system dependencies.
Plus, we've added level mapping options for console sinks, giving you more control over how your logs appear.
Check out the full release notes for migration details:
@hongminhee@hackers.pub
We're excited to announce the release of LogTape 0.9.0! This version brings important improvements to make LogTape more flexible across different JavaScript environments while simplifying configuration for common use cases.
Added synchronous versions of the configuration functions:
configureSync()
: Configure LogTape synchronouslydisposeSync()
: Dispose LogTape resources synchronouslyresetSync()
: Reset LogTape configuration synchronouslyThese functions offer a simpler API for scenarios where async operations aren't needed, allowing for more straightforward code without awaiting promises. Note that these functions cannot use sinks or filters that require asynchronous disposal (such as stream sinks), but they work perfectly for most common logging configurations.
import { configureSync, getConsoleSink } from "@logtape/logtape";
configureSync({
sinks: {
console: getConsoleSink(),
},
loggers: [
{
category: "my-app",
lowestLevel: "info",
sinks: ["console"],
},
],
});
ConsoleSinkOptions.levelMap
option for customizing how log levels are mapped to console methodsTo improve runtime compatibility, file-related sinks have been moved to the @logtape/file
package:
getFileSink()
function to @logtape/file
packageFileSinkOptions
interface to @logtape/file
packagegetRotatingFileSink()
function to @logtape/file
packageRotatingFileSinkOptions
interface to @logtape/file
packageThis architectural change ensures the core @logtape/logtape
package is fully compatible with all JavaScript runtimes, including browsers and edge functions, without introducing file system dependencies. You'll now enjoy better compatibility with bundlers like Webpack, Rollup, and Vite that previously had issues with the file system imports.
If you were using file sinks, update your imports:
// Before
import { getFileSink, getRotatingFileSink } from "@logtape/logtape";
// After
import { getFileSink, getRotatingFileSink } from "@logtape/file";
Don't forget to install the new package:
# For npm, pnpm, Yarn, Bun
npm add @logtape/file
# For Deno
deno add jsr:@logtape/file
This release represents our ongoing commitment to making LogTape the most flexible and developer-friendly logging solution for JavaScript and TypeScript applications. We're continuing to improve performance and extend compatibility across the JavaScript ecosystem.
Special thanks to Murph Murphy for their valuable contribution to this release.
As always, we welcome your feedback and contributions! Feel free to open issues or pull requests on our GitHub repository.
Happy logging!
@hongminhee@hollo.social
Just released #LogTape 0.9.0! 🎉
This version brings two major improvements to our zero-dependency #logging library for #TypeScript:
New Synchronous Configuration API: You can now configure LogTape synchronously with configureSync()
, disposeSync()
, and resetSync()
. Perfect for simpler setups where you don't need async
operations!
Better Runtime Compatibility: We've moved all file-related components to a separate @logtape/file
package. This means the core package now works flawlessly across all JavaScript environments—browsers, edge functions, and various bundlers without any file system dependencies.
Plus, we've added level mapping options for console sinks, giving you more control over how your logs appear.
Check out the full release notes for migration details:
@hongminhee@hackers.pub
We're excited to announce the release of LogTape 0.9.0! This version brings important improvements to make LogTape more flexible across different JavaScript environments while simplifying configuration for common use cases.
Added synchronous versions of the configuration functions:
configureSync()
: Configure LogTape synchronouslydisposeSync()
: Dispose LogTape resources synchronouslyresetSync()
: Reset LogTape configuration synchronouslyThese functions offer a simpler API for scenarios where async operations aren't needed, allowing for more straightforward code without awaiting promises. Note that these functions cannot use sinks or filters that require asynchronous disposal (such as stream sinks), but they work perfectly for most common logging configurations.
import { configureSync, getConsoleSink } from "@logtape/logtape";
configureSync({
sinks: {
console: getConsoleSink(),
},
loggers: [
{
category: "my-app",
lowestLevel: "info",
sinks: ["console"],
},
],
});
ConsoleSinkOptions.levelMap
option for customizing how log levels are mapped to console methodsTo improve runtime compatibility, file-related sinks have been moved to the @logtape/file
package:
getFileSink()
function to @logtape/file
packageFileSinkOptions
interface to @logtape/file
packagegetRotatingFileSink()
function to @logtape/file
packageRotatingFileSinkOptions
interface to @logtape/file
packageThis architectural change ensures the core @logtape/logtape
package is fully compatible with all JavaScript runtimes, including browsers and edge functions, without introducing file system dependencies. You'll now enjoy better compatibility with bundlers like Webpack, Rollup, and Vite that previously had issues with the file system imports.
If you were using file sinks, update your imports:
// Before
import { getFileSink, getRotatingFileSink } from "@logtape/logtape";
// After
import { getFileSink, getRotatingFileSink } from "@logtape/file";
Don't forget to install the new package:
# For npm, pnpm, Yarn, Bun
npm add @logtape/file
# For Deno
deno add jsr:@logtape/file
This release represents our ongoing commitment to making LogTape the most flexible and developer-friendly logging solution for JavaScript and TypeScript applications. We're continuing to improve performance and extend compatibility across the JavaScript ecosystem.
Special thanks to Murph Murphy for their valuable contribution to this release.
As always, we welcome your feedback and contributions! Feel free to open issues or pull requests on our GitHub repository.
Happy logging!
@hongminhee@hollo.social
Just released #LogTape 0.9.0! 🎉
This version brings two major improvements to our zero-dependency #logging library for #TypeScript:
New Synchronous Configuration API: You can now configure LogTape synchronously with configureSync()
, disposeSync()
, and resetSync()
. Perfect for simpler setups where you don't need async
operations!
Better Runtime Compatibility: We've moved all file-related components to a separate @logtape/file
package. This means the core package now works flawlessly across all JavaScript environments—browsers, edge functions, and various bundlers without any file system dependencies.
Plus, we've added level mapping options for console sinks, giving you more control over how your logs appear.
Check out the full release notes for migration details:
@hongminhee@hackers.pub
We're excited to announce the release of LogTape 0.9.0! This version brings important improvements to make LogTape more flexible across different JavaScript environments while simplifying configuration for common use cases.
Added synchronous versions of the configuration functions:
configureSync()
: Configure LogTape synchronouslydisposeSync()
: Dispose LogTape resources synchronouslyresetSync()
: Reset LogTape configuration synchronouslyThese functions offer a simpler API for scenarios where async operations aren't needed, allowing for more straightforward code without awaiting promises. Note that these functions cannot use sinks or filters that require asynchronous disposal (such as stream sinks), but they work perfectly for most common logging configurations.
import { configureSync, getConsoleSink } from "@logtape/logtape";
configureSync({
sinks: {
console: getConsoleSink(),
},
loggers: [
{
category: "my-app",
lowestLevel: "info",
sinks: ["console"],
},
],
});
ConsoleSinkOptions.levelMap
option for customizing how log levels are mapped to console methodsTo improve runtime compatibility, file-related sinks have been moved to the @logtape/file
package:
getFileSink()
function to @logtape/file
packageFileSinkOptions
interface to @logtape/file
packagegetRotatingFileSink()
function to @logtape/file
packageRotatingFileSinkOptions
interface to @logtape/file
packageThis architectural change ensures the core @logtape/logtape
package is fully compatible with all JavaScript runtimes, including browsers and edge functions, without introducing file system dependencies. You'll now enjoy better compatibility with bundlers like Webpack, Rollup, and Vite that previously had issues with the file system imports.
If you were using file sinks, update your imports:
// Before
import { getFileSink, getRotatingFileSink } from "@logtape/logtape";
// After
import { getFileSink, getRotatingFileSink } from "@logtape/file";
Don't forget to install the new package:
# For npm, pnpm, Yarn, Bun
npm add @logtape/file
# For Deno
deno add jsr:@logtape/file
This release represents our ongoing commitment to making LogTape the most flexible and developer-friendly logging solution for JavaScript and TypeScript applications. We're continuing to improve performance and extend compatibility across the JavaScript ecosystem.
Special thanks to Murph Murphy for their valuable contribution to this release.
As always, we welcome your feedback and contributions! Feel free to open issues or pull requests on our GitHub repository.
Happy logging!
@hongminhee@hollo.social
Just released #LogTape 0.9.0! 🎉
This version brings two major improvements to our zero-dependency #logging library for #TypeScript:
New Synchronous Configuration API: You can now configure LogTape synchronously with configureSync()
, disposeSync()
, and resetSync()
. Perfect for simpler setups where you don't need async
operations!
Better Runtime Compatibility: We've moved all file-related components to a separate @logtape/file
package. This means the core package now works flawlessly across all JavaScript environments—browsers, edge functions, and various bundlers without any file system dependencies.
Plus, we've added level mapping options for console sinks, giving you more control over how your logs appear.
Check out the full release notes for migration details:
@hongminhee@hackers.pub
We're excited to announce the release of LogTape 0.9.0! This version brings important improvements to make LogTape more flexible across different JavaScript environments while simplifying configuration for common use cases.
Added synchronous versions of the configuration functions:
configureSync()
: Configure LogTape synchronouslydisposeSync()
: Dispose LogTape resources synchronouslyresetSync()
: Reset LogTape configuration synchronouslyThese functions offer a simpler API for scenarios where async operations aren't needed, allowing for more straightforward code without awaiting promises. Note that these functions cannot use sinks or filters that require asynchronous disposal (such as stream sinks), but they work perfectly for most common logging configurations.
import { configureSync, getConsoleSink } from "@logtape/logtape";
configureSync({
sinks: {
console: getConsoleSink(),
},
loggers: [
{
category: "my-app",
lowestLevel: "info",
sinks: ["console"],
},
],
});
ConsoleSinkOptions.levelMap
option for customizing how log levels are mapped to console methodsTo improve runtime compatibility, file-related sinks have been moved to the @logtape/file
package:
getFileSink()
function to @logtape/file
packageFileSinkOptions
interface to @logtape/file
packagegetRotatingFileSink()
function to @logtape/file
packageRotatingFileSinkOptions
interface to @logtape/file
packageThis architectural change ensures the core @logtape/logtape
package is fully compatible with all JavaScript runtimes, including browsers and edge functions, without introducing file system dependencies. You'll now enjoy better compatibility with bundlers like Webpack, Rollup, and Vite that previously had issues with the file system imports.
If you were using file sinks, update your imports:
// Before
import { getFileSink, getRotatingFileSink } from "@logtape/logtape";
// After
import { getFileSink, getRotatingFileSink } from "@logtape/file";
Don't forget to install the new package:
# For npm, pnpm, Yarn, Bun
npm add @logtape/file
# For Deno
deno add jsr:@logtape/file
This release represents our ongoing commitment to making LogTape the most flexible and developer-friendly logging solution for JavaScript and TypeScript applications. We're continuing to improve performance and extend compatibility across the JavaScript ecosystem.
Special thanks to Murph Murphy for their valuable contribution to this release.
As always, we welcome your feedback and contributions! Feel free to open issues or pull requests on our GitHub repository.
Happy logging!
@hongminhee@hollo.social
Haven't talked about LogTape in a while—it's a #logging library I made for #JavaScript and #TypeScript. You know how logging can be a pain point in JavaScript/TypeScript development? Well, I tried to address some common frustrations.
We've all been there with dependency hell, right? #LogTape has absolutely no external dependencies. Install it without worrying about bloating your node_modules.
You can organize your logs in a tree structure. Want to save only database-related logs to a file? Easy to do. Child categories can inherit settings from their parents too, which keeps things clean and manageable.
Writing a library and want to include logs without stepping on your users' toes? LogTape lets you add logging to your library while giving end users complete control over how those logs are handled.
Plain text logs not cutting it? LogTape supports structured logging. Makes log analysis way easier down the road.
Works smoothly in Node.js, Deno, Bun, browsers, and even edge functions. No special configuration needed.
Check out https://logtape.org/ if you're interested in learning more.
@hongminhee@hollo.social
Haven't talked about LogTape in a while—it's a #logging library I made for #JavaScript and #TypeScript. You know how logging can be a pain point in JavaScript/TypeScript development? Well, I tried to address some common frustrations.
We've all been there with dependency hell, right? #LogTape has absolutely no external dependencies. Install it without worrying about bloating your node_modules.
You can organize your logs in a tree structure. Want to save only database-related logs to a file? Easy to do. Child categories can inherit settings from their parents too, which keeps things clean and manageable.
Writing a library and want to include logs without stepping on your users' toes? LogTape lets you add logging to your library while giving end users complete control over how those logs are handled.
Plain text logs not cutting it? LogTape supports structured logging. Makes log analysis way easier down the road.
Works smoothly in Node.js, Deno, Bun, browsers, and even edge functions. No special configuration needed.
Check out https://logtape.org/ if you're interested in learning more.
@hongminhee@hollo.social
Haven't talked about LogTape in a while—it's a #logging library I made for #JavaScript and #TypeScript. You know how logging can be a pain point in JavaScript/TypeScript development? Well, I tried to address some common frustrations.
We've all been there with dependency hell, right? #LogTape has absolutely no external dependencies. Install it without worrying about bloating your node_modules.
You can organize your logs in a tree structure. Want to save only database-related logs to a file? Easy to do. Child categories can inherit settings from their parents too, which keeps things clean and manageable.
Writing a library and want to include logs without stepping on your users' toes? LogTape lets you add logging to your library while giving end users complete control over how those logs are handled.
Plain text logs not cutting it? LogTape supports structured logging. Makes log analysis way easier down the road.
Works smoothly in Node.js, Deno, Bun, browsers, and even edge functions. No special configuration needed.
Check out https://logtape.org/ if you're interested in learning more.
@hongminhee@hollo.social
Haven't talked about LogTape in a while—it's a #logging library I made for #JavaScript and #TypeScript. You know how logging can be a pain point in JavaScript/TypeScript development? Well, I tried to address some common frustrations.
We've all been there with dependency hell, right? #LogTape has absolutely no external dependencies. Install it without worrying about bloating your node_modules.
You can organize your logs in a tree structure. Want to save only database-related logs to a file? Easy to do. Child categories can inherit settings from their parents too, which keeps things clean and manageable.
Writing a library and want to include logs without stepping on your users' toes? LogTape lets you add logging to your library while giving end users complete control over how those logs are handled.
Plain text logs not cutting it? LogTape supports structured logging. Makes log analysis way easier down the road.
Works smoothly in Node.js, Deno, Bun, browsers, and even edge functions. No special configuration needed.
Check out https://logtape.org/ if you're interested in learning more.
@hongminhee@hollo.social
Haven't talked about LogTape in a while—it's a #logging library I made for #JavaScript and #TypeScript. You know how logging can be a pain point in JavaScript/TypeScript development? Well, I tried to address some common frustrations.
We've all been there with dependency hell, right? #LogTape has absolutely no external dependencies. Install it without worrying about bloating your node_modules.
You can organize your logs in a tree structure. Want to save only database-related logs to a file? Easy to do. Child categories can inherit settings from their parents too, which keeps things clean and manageable.
Writing a library and want to include logs without stepping on your users' toes? LogTape lets you add logging to your library while giving end users complete control over how those logs are handled.
Plain text logs not cutting it? LogTape supports structured logging. Makes log analysis way easier down the road.
Works smoothly in Node.js, Deno, Bun, browsers, and even edge functions. No special configuration needed.
Check out https://logtape.org/ if you're interested in learning more.
@tutam@fediscience.org
Dearest Fediverse (and apologies for the absence),
my book "Hard Work: Producing places, relations and value on a Papua New Guinea resource frontier" was just recently published in full digital open access. (Print-on-demand and oa epub out soon!)
https://hup.fi/site/books/m/10.33134/HUP-29/
"Hard Work explores the complexities of natural resource extraction, looking at both large-scale processes and personal human-environment interactions. It combines a political ecology focus on the connection between environmental issues and power relations with a focus on how value is produced, represented, and materialized."
#OpenAccess #anthropology #PoliticalEcology #PapuaNewGuinea #NaturalResources #LandUse #SwiddenHorticulture #logging #OilPalm
@hongminhee@fosstodon.org · Reply to 洪 民憙 (Hong Minhee)'s post
#LogTape 0.7.0をリリースしました!
新機能の暗黙的コンテキストにより、リクエストID、ユーザーIDなどの文脈情報を、手動で渡すことなくログに自動的に含められるようになりました。
詳しくは記事をご覧ください:
@hongminhee@fosstodon.org
Just released #LogTape 0.7.0 with implicit contexts! Now you can automatically include request IDs, user IDs, and more in your logs without passing context manually. Read more about this powerful feature:
https://dev.to/hongminhee/introducing-implicit-contexts-in-logtape-070-57fi
@Bentley@canada.masto.host
Activists shared a win with the #Kananaskis logging slowdown last year, temporarily saving 2000 football fields worth of climate-preserving forest & trails but for how long & what comes next? We asked the Hub's Jenny Yeremiy & Joshua Killeen of #CPAWS.
PODCAST: https://www.podcastics.com/episode/309464/link/
#Kananaskis #Clearcut #Logging #Forests #biodiversity #Climate #watersheds #NaturalCapital
@hongminhee@fosstodon.org
Version 0.5.0 of #LogTape, the zero-dependency #logging library for #Deno, #Node.js, #Bun, edge functions, and browsers, has been released! The main additions include:
• Contexts
• ANSI color formatter
• Comprehensive docs
• A few API conveniences
LogTape v0.5.0 is available from JSR and npm:
• JSR: https://jsr.io/@logtape/logtape@0.5.0
• npm: https://www.npmjs.com/package/@logtape/logtape/v/0.5.0
In addition, a new website with documentation has been launched, so please check it out!
@hongminhee@fosstodon.org
In the next version of #LogTape, a zero-dependency #logging library for #JavaScript & #TypeScript, contexts will be introduced that allow the same set of properties to be shared across multiple log messages. Thanks to @okikio for collaborating on the design! This feature is available for preview in 0.5.0-dev.60+f819929c.
• JSR: https://jsr.io/@logtape/logtape@0.5.0-dev.60+f819929c
• npm: https://www.npmjs.com/package/@logtape/logtape/v/0.5.0-dev.60
@lynn_sh@tech.lgbt
@joaopinheiro@kolektiva.social
New Images Show Largest Uncontacted Indigenous Tribe on Earth Dangerously Close to Loggers in Peruvian Amazon
#Anarchism #Freedom #Tribe #Murder #HumanRights #indigenousPeoples #Peru #Logging #Rainforests https://www.ecowatch.com/indigenous-tribe-amazon-peru-logging.html
@hongminhee@fosstodon.org
Released v0.4.2 of #LogTape, which is a zero-dependency #logging library for #TypeScript & #JavaScript! Since this version, it work well on #Cloudflare Workers out of box!
• JSR: https://jsr.io/@logtape/logtape@0.4.2
• npm: https://www.npmjs.com/package/@logtape/logtape/v/0.4.2
@fedify@hollo.social
#Fedify offers robust logging capabilities through integration with LogTape. This feature allows you to easily debug and monitor your Fedify app!
To enable #logging, simply install the @logtape/logtape
package and configure it in your app's entry point:
import { configure, getConsoleSink } from "@logtape/logtape";
await configure({
sinks: { console: getConsoleSink() },
filters: {},
loggers: [
{ category: "your-app", sinks: ["console"], level: "debug" },
{ category: "fedify", sinks: ["console"], level: "info" },
],
});
Fedify uses hierarchical categories for fine-grained control over log output. Key categories include ["fedify", "federation", "http"]
for HTTP requests/responses and ["fedify", "federation", "inbox"]
/["fedify", "federation", "outbox"]
for incoming/outgoing activities. (There are more categories.)
With #LogTape integration, you gain valuable insights into your Fedify app's behavior, making troubleshooting and optimization much more straightforward!
@log4jmc@infosec.exchange
I've been enjoying infosec.exchange for the last month or so but have been putting off an #Introduction because I'm awkward and anxious (#privacy am I right?). I feel more comfortable talking about my cat than myself or my work on social media, so you'll probably mostly see him amongst my boosts and replies. He's a little hacker who tricks me into FaceID unlocking my iPad for him or hides my pouch of physical security keys to remind me not to be careless with them.
See how I just went on about the cat? Yeah... I feel imposter syndrome about belonging in #InfoSec. I'm an IT #security and #operations focused #SysAdmin (#BlueTeam) whose been fascinated/working with computers since I was 3, and have been doing it professionally for over 10 years now. Does that make me #SecOps? I honestly don't know. I love this community though and want to make an effort to share what I do know more often besides the cat pics or conversations or boosting #ThreatIntel and news I think to share.
If I had to sum up in a few hashtags and such, I know securing #Windows and #ActiveDirectory best but I use/protect #Linux and #macOS if you'll forgive me for using #PowerShell there too. I love #scripting and #automation, the #OSINT and #ThreatIntel and #IOCs we share, #infrastructure and #firewall stuff, #logging and #DFIR, and reading/writing reports just as much as code. I'm not super passionate about the #cloud but that's not a hill I'd die on and #Azure is pretty cool.
Did I mention I have one of the best #CatsOfInfoSec ever?
Anyway, "it's me, hi!"