Results for split-config-generator

Generate split configs for use with test-boosters

No description provided.

Split a string on the first occurance of a given separator

Easy way to split a string on a given character unless it's quoted or escaped.

Transform a string between `camelCase`, `PascalCase`, `Capital Case`, `snake_case`, `kebab-case`, `CONSTANT_CASE` and others

Generate JSON schema from your Typescript sources

split a Text Stream into a Line Stream, using Stream 3

split a Text Stream into a Line Stream

Cypress test reporter for CircleCI

Split a LineString by another GeoJSON Feature.

Split Cypress specs across parallel CI machines for speed

Determine if a function is a native generator function.

The easiest way to generate custom Apple Wallet passes in Node.js

Turns an AST into code.

Split string by any separator excluding brackets, quotes and escaped characters

Turn async generator functions into ES2015 generators

Helper function to remap async functions to generators

A function that returns the normally hidden `GeneratorFunction` constructor

Turn async functions into ES2015 generators

Zero-config PWA Assets Generator

Core Minecraft API Docs Generator package for generating API markup and documentation

React component for Split.js

Split JavaScript SDK common components

Simple module to split a single certificate authority chain file (aka: bundle, ca-bundle, ca-chain, etc.) into an array, as expected by the node.js tls api.

<p>Sass or the much better approach of scss is really helpful and a big silver bullet for my css structuring in ruby projects.</p> \ <p>Standard sass command works for whole directories or single files only. In general it gets the jobs we want done, but in practical usage i think the sass command tool is a little bit unconvinient. A common scenario for me is, \ that you have whole bunch of sass files, which you want to compile to a single compressed output file. But if you have splitted your sass files in component based modules and you want to watch the complete folder you have to care for dependency handling in each file, because each file will be compiled for its own.</p> \ <pre># compiling a complete folder with scss ~ $ sass css/scss:css/compiled</pre> \ <p>So converting the whole folder is not what i want, because i don\'t want to import for example my color.sass config file in each module again. Compiling a single file seems to be the better solution, and it works in general, as expected, but the devil is in the detail. </p> <pre># compiling a single file where the other files are imported. ~ $ sass css/scss/main.scss:css/compiled/main.css</pre> \ <p>If we change a file with impact to our main.sass file, the --watch handle will not get it, because it observes only the timestamp of the given main.sass.</p> <p>Here is it, where mindful_sass tries to help out. You use it according to the single file variant of sass, but it tries to observe the whole folder the given sass file is placed. If a timestamp of file in the sass folder or its children changes it will compile the specified main.sass again.</p> \ <p>This gem is not aimed to replace anything in the sass universe. It is only a wrapper to avoid the described unconvinience, and i hope that it gets useless as fast as possible, because the sass development gets this feature done for themselves.</p> \ <p>Thanks anyway to the sass developer team.</p>