joewalnes / crunchicorn Goto Github PK

When I try to run the command I get this error.

ERROR [Error: Couldn't find preset "es2015-rollup" relative to directory "...."]

Then when i installed that npm module i get this error:

ERROR { [Error: Cannot find module 'babel-runtime/helpers/interop-require-default'] code: 'MODULE_NOT_FOUND' }

Then Finally when i have that installed i get this error:

ERROR [Error: Couldn't find preset "stage-3" relative to directory "/Users/tal/Projects/sitefs/site"]

Although this is implemented in Node, that should never be of concern to the user. At the moment, the only way to install though is via npm. Create a distribution for users who don't have npm/node available. This would be a completely self contained package.

Get into major package managers like brew, ubuntu ppa, etc.

Error handling is pretty ugly at the moment. Make it look nice on the console. With color if running on a tty.

The goal of hot reloading is to allow code changes to propagate to the browser without forcing a refresh. This allows insanely fast feedback loops for UI changes.

This is a placeholder for a discussion on how to implement it.

One thing I don't want to do is force users to have to run a custom development server. This tightly couples users to Node based apps and doesn't support the needs of other server side web stacks (e.g. Rails, PHP, Go, Java, etc...).

Also, users should not have to write any additional code to get this to work. It should simply be a matter of --hot.

My preference is for hot loading to be provided by the browser developer tools, and should not require bundling additional code into a web-app. There may have to be a small out of band trigger that the cmd line tool can use to notify the browser that it should refresh the code and trigger a render.

Implement --watch (alias -w) cmd line option to keep running and watch files.

Lessons learned from other tools:

• Console should give feedback about when changes detected, output ready, errors, etc
• Allow multiple watches to run at once (e.g. in1.js out1.js in2.js out2.js
• Support custom completion cmd line hooks for success and error (which may send notifications, perform post processing build steps, etc)
• If errors occur, propagate the messages to the browser so they don't go unnoticed
• Avoid polling where possible: use notifications if filesystem supports it

In the same way we can do in.js out.js, also support in.css out.css, which applies the same CSS rules but doesn't use the custom JS injector.

This is a feature for GNU make users that will greatly speed up the builds. If users don't use Make, they don't need to know about it.

Cmd line flag to generate a foo.depends file that can be included in a project Makefile. This list all files involved in creating the file output (including sources, transitive sources, third party libs, package.json, etc). When Make is run again, it can check the staleness of these files and only build if any of these have changed.

http://www.gnu.org/software/make/manual/html_node/Automatic-Prerequisites.html