Generate the Node.js LTS schedule
A base TSConfig for working with Node LTS (24).
Resolve Node.js version aliases like 'latest', 'lts' or 'erbium'
LTS package, Officially supported by SSLCommerz Integration Team.
Huaweicloud SDK for lts
The LTS schedule in JSON. Extracted from https://github.com/nodejs/LTS
[](https://www.npmjs.com/package/@brickhouse-tech/angular-lts) [](https://www.npmjs.com/package/@
Angular (LTS) module to resize images files in browser
lts-web-sdk
Centralizes NodeJS LTS version cross project
Get the latest (LTS) node.js version and versions of its modules.
systools-lts 2.0
Babel preset for ES2015 in Node v4 LTS (Argon).
lts-mini-sdk
Get the maintained LTS versions of Node.js
Pure javascript implementation of Zlib nodejs core module. The zlib module provides compression functionality implemented using Gzip, Deflate/Inflate, and Brotli. Compatible with Node.js 22.x LTS.
Personal preset for general TypeScript settings. To be used in conjunction with a TSConfig for the specific platform (e.g. @tsconfig/node-lts)
TypeScript configuration for Node.js LTS
Tool to install/uninstall the LTS ecosystem packages
Replace text patterns with applause.
**⚠️ LoopBack 3 is in Maintenance LTS mode, only critical bugs and critical security fixes will be provided. (See [Module Long Term Support Policy](#module-long-term-support-policy) below.)**
migration tool for sequelize & typescript users
The recommended Node.js version to run it is `20.11.1 LTS`.
Check if the current node version is a LTS release
Yank other people's crates. Helpful for using old compilers and avoiding broken deps
Implements labelled transition systems for various I/O formats using a general LTS trait.
operations on local timestamps
An event-driven, non-blocking I/O platform for writing asynchronous I/O backed applications.
An event-driven, non-blocking I/O platform for writing asynchronous I/O backed applications.
Reducing and comparing labelled transition systems modulo various bisimulation equivalences
An event-driven, non-blocking I/O platform for writing asynchronous I/O backed applications.
An event-driven, non-blocking I/O platform for writing asynchronous I/O backed applications.
See `lts` crate
An expression engine written in pure rust (LTS)
Huawei Cloud API definitions, generated from OpenAPI spec
Node.js tool support for vx
Configure RuboCop + a bevy of friends to gradually lint Ruby code
Enables Ruby projects to more confidently support even the most finely-aged Rubies. Part of the rubocop-lts family.
A collection of fixes to make some old gems Ruby 2.3+ compatible.
Fluentd plugin to upload logs to Azure Storage append blobs. Fork of https://github.com/microsoft/fluent-plugin-azure-storage-append-blob
Enables Ruby projects that test with RSpec to more confidently support even the most finely-aged Rubies. Part of the rubocop-lts family.
fluent-package v5 LTSのリリースについて紹介するスライドです。
Have you ever wanted to call <code>exit()</code> with an error condition, but weren't sure what exit status to use? No? Maybe it's just me, then. Anyway, I was reading manpages late one evening before retiring to bed in my palatial estate in rural Oregon, and I stumbled across <code>sysexits(3)</code>. Much to my chagrin, I couldn't find a +sysexits+ for Ruby! Well, for the other 2 people that actually care about <code>style(9)</code> as it applies to Ruby code, now there is one! Sysexits is a *completely* *awesome* collection of human-readable constants for the standard (BSDish) exit codes, used as arguments to +exit+ to indicate a specific error condition to the parent process. It's so fantastically fabulous that you'll want to fork it right away to avoid being thought of as that guy that's still using Webrick for his blog. I mean, <code>exit(1)</code> is so passé! This is like the 14-point font of Systems Programming. Like the C header file from which this was derived (I mean forked, naturally), error numbers begin at <code>Sysexits::EX__BASE</code> (which is way more cool than plain old +64+) to reduce the possibility of clashing with other exit statuses that other programs may already return. The codes are available in two forms: as constants which can be imported into your own namespace via <code>include Sysexits</code>, or as <code>Sysexits::STATUS_CODES</code>, a Hash keyed by Symbols derived from the constant names. Allow me to demonstrate. First, the old way: exit( 69 ) Whaaa...? Is that a euphemism? What's going on? See how unattractive and... well, 1970 that is? We're not changing vaccuum tubes here, people, we're <em>building a totally-awesome future in the Cloud™!</em> include Sysexits exit EX_UNAVAILABLE Okay, at least this is readable to people who have used <code>fork()</code> more than twice, but you could do so much better! include Sysexits exit :unavailable Holy Toledo! It's like we're writing Ruby, but our own made-up dialect in which variable++ is possible! Well, okay, it's not quite that cool. But it does look more Rubyish. And no monkeys were patched in the filming of this episode! All the simpletons still exiting with icky _numbers_ can still continue blithely along, none the wiser.
Zencoder <http://zencoder.com> integration library.
Fluxxor is a set of Flux architecture tools for React. This gem makes it available for the Rails asset pipeline.
Fluentd plugin to upload logs to Azure Storage append blobs. Fork of https://github.com/microsoft/fluent-plugin-azure-storage-append-blob
This gem comes from a fork of https://github.com/rails-lts/jquery-rails, the difference being that it will be kept up to date with the further upstream https://github.com/rails/jquery-rails
Pure Ruby implementation of Array#dig and Hash#dig for Ruby < 2.3.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.