Plain Code — visual AI workspace for developers. Preview, idea capture, and auto-commit. Part of Plain Office.
Protobuf-like i18n from plain code
Protobuf-like i18n from plain code: Svelte adapter
Protobuf-like i18n from plain code: JSX adapter
Plain code doctrine package published by kamilchm
Protobuf-like i18n from plain code: JSON storage driver
Check if a value is a plain object
Returns true if an object was created by the `Object` constructor, or Object.create(null).
Check if a value is an object
This package contains rich text helpers for Lexical.
Test if a value is a plain object.
This package contains plain text helpers for Lexical.
Generate or verify a Proof Key for Code Exchange (PKCE) challenge pair
[](https://npm-stat.com/charts.html?package=@sanity/visual-editing) [](https://
A tiny (2.8kB) and fast utility for getting a MIME type from an extension or filename
Copy stuff into clipboard using JS with fallbacks
A function to recursively extract files and their object paths within a value, replacing them with null in a deep clone without mutating the original value. FileList instances are treated as File instance arrays. Files are typically File and Blob instance
Tiny and elegant HTTP client based on the Fetch API
file downloading using client-side javascript
A comprehensive library for mime-type mapping
hast utility to get the plain-text value of a node
Returns true if a value is a plain object, array or function.
A JavaScript Regular Expression library, extending the standard RegExp class with missing functionality
Replace loader for Webpack
Sourcery puts a spell-casting layer between the code you write and the code you ship. Using ERB templating in this layer lets you write highly meta-magical code.
This Jekyll plugin generates pretty or plain Markdown and/or HTML source code pages for your Markdown docs, which you can easily link to for viewing.
Minimal, plain old ruby gem to work with Sepa Reason Codes.
Configuration as code for GitLab using config in plain YAML
A plain text code snippet manager
Features: * Dynamic, framework-neutral, client-friendly <code>ResourceTemplate</code> metadata describing the path/URI structures of your whole site or of specific resources * A link header-based discovery protocol, enabling clients to find <code>ResourceTemplate</code> metadata from the resources of any enabled controller * Easy integration with Rails * JSON, YAML and XML formats, also a bonus plain text report ATTENTION: 0.8.0 adds Rails integration via Rack middleware; the Rails controller and helpers are hereby deprecated!
Ruby gem allowing you to include re-usable code and partials in html or plain text fields.
Feature flags made simple: turn code on or off with Redis controls, allowing plain enabled/disabled states as well as finer-grained percentage-based control.
Rails plugin. Allows you to write plain SQL migrations without Ruby code.
Wrapper around net-ssh for plain execution of remote shell commands and painless collection of exit codes, stdout, stderr messages.
capture_fu is a small library that facilitates capture of stdout and stderr output, of either subprocesses or plain old Ruby code.
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.
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.