Beautify / pretty print JavaScript and JSON
A pretty JS colorwheel
See nodejs errors with less clutter
Stringify any JavaScript value.
A light logging package for Node.js and Bun applications. Features file logging and beautiful console output.
Fork of pretty-format with support for ESM
Prettifier for Pino log lines
Easily format the time from node.js `process.hrtime`. Works with timescales ranging from weeks to nanoseconds.
process.hrtime() to words
Some tweaks for beautifying HTML with js-beautify according to my preferences.
A node module to convert JSON to YAML
The best of both `JSON.stringify(obj)` and `JSON.stringify(obj, null, indent)`.
Clean up error stack traces
<h1 align="center"> <img alt="" width="75" src="https://github.com/cucumber.png"/> <br> pretty-formatter </h1> <p align="center"> <b>Rich formatting of Cucumber progress and results for the terminal</b> </p>
Convert bytes to a human readable string: 1337 → 1.34 kB
Convert milliseconds to a human readable string: `1337000000` → `15d 11h 23m 20s`
Convert Coffee/CJSX into pretty JS/JSX
[![npm version][npm-v-src]][npm-v-href] [![npm downloads][npm-d-src]][npm-d-href] [![status][github-actions-src]][github-actions-href]
Pretty formatter for ESLint
[![npm version][npm-v-src]][npm-v-href] [![npm downloads][npm-d-src]][npm-d-href] [![status][github-actions-src]][github-actions-href]
Get Pretty Quick
Convert an object or array into a formatted string
for adding, subtracting, and indexing discontinuous ranges of numbers
Pretty js package
Utility for pretty printing JSON while preserving the order of keys and the original indentation and line endings from a JSON source.
Easy way to emit prettified JSON body via reqwest::RequestBuilder
Miniparser works pretty simply. You pass the Gem some input (HTML, JS, or CSS), and it will validate it, return the validated status, then minify it, and return the minified version as either a file (path) and a text return, respective to what input it got
== E9Tags An extension to ActsAsTaggableOn[http://github.com/mbleigh/acts-as-taggable-on] which "improves" on custom tagging, or at least makes it more dynamic. Additionally it provides some autocomplete rack apps and the corresponding javascript. == Installation 1. E9Tags requires jquery and jquery-ui for the autocompletion and tag-adding form, be sure they're loaded in your pages where the tags form will be rendered. 2. E9Tags extends ActsAsTaggableOn and requires it. Run it's generator if you have not. 3. Run the E9Tags install script to copy over the required JS rails g e9_tags:install 4. Then make sure it is loaded, how you do that doesn't matter, e.g. <%= javascript_include_tag 'e9_tags' %> 5. Create an initializer for that sets up the taggable models and their controllers. This gives the models the tag associations and methods and prepares their controller to handle the otherwise unexpected tag params. require 'e9_tags' require 'contacts_controller' require 'contact' E9Tags.controllers << ContactsController E9Tags.models << Contact OR You can just include the modules in your classes yourself. The first way really exists for the case where the classes you wish to extend are part of another plugin/gem. # in contact.rb include E9Tags:Model # in contacts_controller.rb include E9Tags::Controller 6. Render the tags form partial in whatever model forms require it. = render 'e9_tags/form', :f => f If you pass a context, it will be locked and no longer possible to change/add the contexts on the form (and as a side effect, the tags autocompletion will be restricted to that context). = render 'e9_tags/form', :f => f, :context => :users Finally if you pass a 2nd arg to :context you can set a tag context to be "private" (default is false). In this case the tag context will be locked as private (typically suffixed with *), meaning that the tags will not be publicly searchable/visible. This is useful for organizational tags tags, say if you wanted to arbitrarily group records, or create a custom search based on a tag context. = render 'e9_tags/form', :f => f, :context => [:users, true] NOTE: The form and javascript are intended to work out of the box, but the certainly aren't going to look pretty. If you do intend to use the forms, you'll no doubt need to style them.
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.