## Project setup ``` npm install ```
Distributed locking and slashing protection for Aztec validators running in high-availability configurations.
Support for representing 64-bit integers in JavaScript
Parse and stringify JSON with comments. It will retain comments even after saved!
Callback wrapping utility
Fast (and loose) selective `process.env` replacer using js-tokens instead of an AST
A state machine compiler
Port of C's wcwidth() and wcswidth()
Generic JSDoc-like comment parser
Use node's fs.realpath, but fall back to the JS implementation if the native one fails
Bare simple logger for NodeJS
TypeScript definitions for fluent-ffmpeg
Discard comments in your CSS files with PostCSS.
An arbitrary-precision Decimal type for JavaScript.
The Node.js `util.deprecate()` function with browser support
Resolve any installed ES6 compatible promise
PostCSS plugin to replace overflow-wrap with word-wrap or optionally retain both declarations.
Get the shortest leading whitespace from lines in a string
A very simple and stupid parser, based on a statemachine and regular expressions.
a set of utilities to work with JSON / JSON5 documents
PostCSS plugin for CSS Modules to pass arbitrary values between your module files
CSS box-shadow parser and stringifier
Simple module to infer the root directory of the currently running node application
Parse and display moments in any timezone.
This gem will check if there the code has sufficient amount of comments. This can be used in tools such as Jenkins to check if the comment meets the expected quantity.
Although made popular by Windows, INI files can be used on any system thanks to their flexibility. They allow a program to store configuration data, which can then be easily parsed and changed. Two notable systems that use the INI format are Samba and Trac. More information about INI files can be found on the [Wikipedia Page](http://en.wikipedia.org/wiki/INI_file). ### Properties The basic element contained in an INI file is the property. Every property has a name and a value, delimited by an equals sign *=*. The name appears to the left of the equals sign and the value to the right. name=value ### Sections Section declarations start with *[* and end with *]* as in `[section1]` and `[section2]` shown in the example below. The section declaration marks the beginning of a section. All properties after the section declaration will be associated with that section. ### Comments All lines beginning with a semicolon *;* or a number sign *#* are considered to be comments. Comment lines are ignored when parsing INI files. ### Example File Format A typical INI file might look like this: [section1] ; some comment on section1 var1 = foo var2 = doodle var3 = multiline values \ are also possible [section2] # another comment var1 = baz var2 = shoodle
todo_lint can be integrated into a continuous integration workflow to keep todo comments from becoming stagnant over time. Just annotate the comment with a date, and if that date has passed, your build will fail, and you'll be reminded to snooze the todo a little later, or finally address it.
Scrapes the website tildes.net. Can scrape topics on a page, top level groups, and comments on a topic. Also has a very basic cli for browsing
Styleguides can be a pain to keep as a living documentation for your CSS. By analysing the comments in your SASS files, and by adding markdown to your stylesheets, you can generate a living, breathing documentation styleguide that has examples of how the CSS is used.
Edit you db schema in db/plan.rb file. It has same syntax as rails schema.rb, but you can also leave comments and so on. Then, generate migration, and it will be prefilled with diff between plan.rb and your current db.
This gem enables you to access most features of the Viadeo GRAPH API via Ruby
Find screenshots publicly uploaded to Steam by a particular user or for a particular game. Get details like the title, how many likes and comments it has received, the dimensions and file size, and URLs for different sizes of each screenshot.
Although made popular by Windows, INI files can be used on any system thanks to their flexibility. They allow a program to store configuration data, which can then be easily parsed and changed. Two notable systems that use the INI format are Samba and Trac. More information about INI files can be found on the [Wikipedia Page](http://en.wikipedia.org/wiki/INI_file). ### Properties The basic element contained in an INI file is the property. Every property has a name and a value, delimited by an equals sign *=*. The name appears to the left of the equals sign and the value to the right. name=value ### Sections Section declarations start with *[* and end with *]* as in `[section1]` and `[section2]` shown in the example below. The section declaration marks the beginning of a section. All properties after the section declaration will be associated with that section. ### Comments All lines beginning with a semicolon *;* or a number sign *#* are considered to be comments. Comment lines are ignored when parsing INI files. ### Example File Format A typical INI file might look like this: [section1] ; some comment on section1 var1 = foo var2 = doodle var3 = multiline values \ are also possible [section2] # another comment var1 = baz var2 = shoodle
Sneat admin template is decked with many features to assist you in creating quality apps. The HTML5 template has built-in authentication pages, an organized folder structure, clean and well-commented code, documentation, and a vertical layout.
Compatible with Resque 1.x. Use Resque.push if you are using >= 2.x. Resque is great. So is job processing with redis. Our biggest drawback has been that resque requires the class that will be processing a job to be loaded when the job is enqueued. But what happens when the implementing job is defined in a separate application and isn't currently loaded into memory? Enter Resque Remote. Resque Remote's simple goal is to allow you to add a job to a queue with a string identifier for the class rather than the class constant. It is assumed that the worker-side of the equation _will_ have the class in memory and hence will be able to run it no problem. Feedback, comments and questions are welcome at bj [dot] neilsen [at] gmail [dot] com.
A command line tool and library to generate Swift skeletons from Objective-C code. This tool can be used to "jumpstart" porting from Objective-C to Swift. This tool does not attempt to transliterate from Objective-C to Swift. Instead, the original code is included in comments within the generated Swift skeletons. Swift Version 1.2 syntax is generated at this time. The simple Objective-C pattern matcher is used to capture the constructs that will be ported to Swift. This technique can be confused by complex constructs, but has the advantage that the source code does not have to compile.