humblesoftware / gib Goto Github PK

Define the desired scope of recipes. Eg. for styles, do we want a single css recipe which supports less, sass, stylus etc. transformations or individual recipes for each?

Implications:

• how many recipes we have
• how big each recipe is
• task composition for several pre-processors resulting in a single file (eg. less + stylus -> css)

This applies to source tasks (css, js, templates...).

Consider adding a separate recipe for browserify.

This relates to #6 but is distinct in that it's the pipeline which changes (gulp vs. browserify) instead of the input and set of transformations.

Browserify trask crashes on transform errors (eg. incorrect handlebars syntax).

The server recipe should support robust configuration.

Like parse errors from pipelines we should notify on jshint errors.

I've observed that inline source maps load much slower in chrome than external source maps. Haven't found any insight as to why.

The server recipe should also support proxies.