whatwedo/craffft

File processing wrapper | UNMAINTAINED

craffft's Issues

Add webpack dashboard

Remove gulp dependency

Refactor all stuff to webpack. This doesn't change any functionality, but removes a bloat of dependencies. Also this shouldn't be a breaking change for users of craffft.

Webpack has loaders for all CSS Preprocessors, so this shouldn't be a problem.

Bump to v1.0.0

Since craffft is used productive in a minimum of 5 projects now, it's time to bump to v1.0.0 to make use of semver updating process via npm.

Check for lodash@<2.0.0 dependencies

There are two dependencies which use lodash@<2.0.0. Find them and make pull requests to update them to v3.

Changelog task doesn't replace placeholder in changelog.md

fs: re-evaluating native module sources is not supported.

Track down following message:

(node:13287) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.  

Javascript not compiling on --build

Fix readme

Wrong description of the run commands

watcher doesn't work in vagrant vm's

Add possibility to define bundles

Based on webpack's bundle config, let objects be valid for JavaScript configuration.

Watcher: require(...) is not a function

triggered watcher task: copy

[BS] Watching files...
/vagrant/node_modules/craffft/src/tasks/watch/default.js:50
        require('../' + taskName.replace(':', '/'))()
                                                   ^

TypeError: require(...) is not a function
    at /vagrant/node_modules/craffft/src/tasks/watch/default.js:50:52
    at write (/vagrant/node_modules/gulp-watch/index.js:139:3)
    at /vagrant/node_modules/vinyl-file/index.js:52:4
    at /vagrant/node_modules/graceful-fs/graceful-fs.js:78:16
    at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:445:3)

npm ERR! Linux 3.13.0-88-generic
npm ERR! argv "/home/vagrant/.nvm/versions/node/v6.3.1/bin/node" "/home/vagrant/.nvm/versions/node/v6.3.1/bin/npm" "run" "watch"
npm ERR! node v6.3.1
npm ERR! npm  v3.10.3
npm ERR! code ELIFECYCLE
npm ERR! [email protected] watch: `craffft-watch`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] watch script 'craffft-watch'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the cens-website package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     craffft-watch
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs cens-website
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls cens-website
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /vagrant/npm-debug.log

TypeScript slow with version 1.8

Define all possible options

Define a standard set of available options e.g. flatten, keepComments etc. which are valid for all packages. Then alter config to use this set.

Watch used with proxy does not reload browser

Run/watch exits if new files are added while running

Merge changelog and bump configuration

Since changelog is just like a sub task of bump, it makes sense to merge those configurations.

Watch exits on CSS errors

Add plumber to prevent this.

Check dependencies with slow-deps

slow-deps, a package which allows you to measure which dependencies in a project are slowest to npm install. This package also tells you the size on disk and the total number of transitive dependencies being printed.

The end goal here is to show you the potential number of unnecessary dependencies your project is leaning on, and assist with removing some of the bloat.

Remove autoprefixer from cssnext

Autoprefixer is know included a second time through cssnext. But we use autoprefixer as standalone to process additional results from LESS, Sass and Stylus.

Remove the additional instance in cssnext.