rehabstudio / fe-skeleton Goto Github PK

View Code? Open in Web Editor NEW

16.0 16.0 11.0 275 KB

The official front-end skeleton used by rehabstudio.

License: MIT License

JavaScript 96.17% Makefile 3.83%

fe-skeleton's People

Contributors

Stargazers

Watchers

Forkers

paddycarey kyllle peter-mcconnell grieve hyphengroup letsgojuno mattbilson beautifulpixels adam-etain-software muthhus

fe-skeleton's Issues

Test example in README doesn't work

Copying and pasting the following example into a test doesn't work, the done statement is expecting an explicit trigger of the callback:

// Loading dependencies.
var FeatureModel = require('../src/models/FeatureModel');

describe('The Feature model', function() {

    beforeEach(function() {
        this.testModel = new FeatureModel();
    });

    afterEach(function() {
        this.testModel = null;
    });

    it('should have defaults', function(done) {
        expect(this.testModel.to.have.ownProperty('defaults');
    });

});

HTML cannot be watched.

Watch task needs to be able to watch for HTML changes.

Adding new files need watch to be restarted

Gulp Watch need to be restarted in order to enjoy the new files added. Would be nice to avoid this

Implement browsersync into server build

Keep it simple, few options, simple css injection and reloading after scripts.

browsersync.reload() in gulp pipe after dest.

http://www.browsersync.io/

npm install error on `make fe-setup`

On running make fe-setup I encounter a series of errors. I'm afraid im not that experienced with imagemin / npm / other issues so I can't offer up much in the way of identifying the issue other than pasting the response I got:

npm http 200 https://registry.npmjs.org/assert/-/assert-1.3.0.tgz
/bin/sh: 1: node: not found
gyp: Call to 'node -e "require('nan')"' returned exit status 127. while trying to load binding.gyp
gyp ERR! configure error 
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onCpExit (/usr/share/node-gyp/lib/configure.js:431:16)
gyp ERR! stack     at ChildProcess.EventEmitter.emit (events.js:98:17)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:797:12)
gyp ERR! System Linux 3.13.0-44-generic
gyp ERR! command "nodejs" "/usr/bin/node-gyp" "configure" "build"
gyp ERR! cwd /home/pete/Sites/fe-skeleton/node_modules/gulp-imagemin/node_modules/imagemin/node_modules/imagemin-optipng/node_modules/optipng-bin/node_modules/bin-wrapper/node_modules/download/node_modules/decompress-unzip/node_modules/adm-zip/node_modules/fidonet-mailer-binkp-crypt
gyp ERR! node -v v0.10.25
gyp ERR! node-gyp -v v0.10.10
gyp ERR! not ok 
npm WARN This failure might be due to the use of legacy binary "node"
npm WARN For further explanations, please read
/usr/share/doc/nodejs/README.Debian

npm http GET https://registry.npmjs.org/is-relative
npm http GET https://registry.npmjs.org/isarray/0.0.1
npm http GET https://registry.npmjs.org/core-util-is
npm http GET https://registry.npmjs.org/string_decoder
npm http 304 https://registry.npmjs.org/is-relative
npm http 304 https://registry.npmjs.org/core-util-is
npm http 304 https://registry.npmjs.org/isarray/0.0.1
npm http 304 https://registry.npmjs.org/string_decoder
npm http GET https://registry.npmjs.org/fidonet-mailer-binkp-crypt
npm http 304 https://registry.npmjs.org/fidonet-mailer-binkp-crypt
npm http GET https://registry.npmjs.org/mime-db
npm http GET https://registry.npmjs.org/delayed-stream/0.0.5
npm http 200 https://registry.npmjs.org/mime-db
npm http GET https://registry.npmjs.org/async
npm http 304 https://registry.npmjs.org/delayed-stream/0.0.5
/bin/sh: 1: node: not found
gyp: Call to 'node -e "require('nan')"' returned exit status 127. while trying to load binding.gyp
npm http 304 https://registry.npmjs.org/async
gyp ERR! configure error 
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onCpExit (/usr/share/node-gyp/lib/configure.js:431:16)
gyp ERR! stack     at ChildProcess.EventEmitter.emit (events.js:98:17)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:797:12)
gyp ERR! System Linux 3.13.0-44-generic
gyp ERR! command "nodejs" "/usr/bin/node-gyp" "configure" "build"
gyp ERR! npm http GET https://registry.npmjs.org/mime-db/-/mime-db-1.6.1.tgz
cwd /home/pete/Sites/fe-skeleton/node_modules/grunt-contrib-imagemin/node_modules/imagemin/node_modules/imagemin-gifsicle/node_modules/gifsicle/node_modules/bin-wrapper/node_modules/download/node_modules/decompress-unzip/node_modules/adm-zip/node_modules/fidonet-mailer-binkp-crypt
gyp ERR! node -v v0.10.25
gyp ERR! node-gyp -v v0.10.10
gyp ERR! not ok 
npm WARN This failure might be due to the use of legacy binary "node"
npm WARN For further explanations, please read
/usr/share/doc/nodejs/README.Debian

npm http 200 https://registry.npmjs.org/mime-db/-/mime-db-1.6.1.tgz
npm http GET https://registry.npmjs.org/hawk
npm http GET https://registry.npmjs.org/bl
npm http 304 https://registry.npmjs.org/hawk
npm http 304 https://registry.npmjs.org/bl
npm http GET https://registry.npmjs.org/asn1/0.1.11
npm http GET https://registry.npmjs.org/assert-plus
npm http GET https://registry.npmjs.org/ctype/0.5.3
npm http 304 https://registry.npmjs.org/ctype/0.5.3
npm http 304 https://registry.npmjs.org/assert-plus
npm http 304 https://registry.npmjs.org/asn1/0.1.11
npm http GET https://registry.npmjs.org/nan
npm http 304 https://registry.npmjs.org/nan
npm ERR! error rolling back Error: ENOTEMPTY, rmdir '/home/pete/Sites/fe-skeleton/node_modules/grunt-contrib-imagemin/node_modules/imagemin/node_modules/imagemin-gifsicle/node_modules/gifsicle/node_modules/bin-wrapper/node_modules/download/node_modules'
npm ERR! error rolling back  [email protected] { [Error: ENOTEMPTY, rmdir '/home/pete/Sites/fe-skeleton/node_modules/grunt-contrib-imagemin/node_modules/imagemin/node_modules/imagemin-gifsicle/node_modules/gifsicle/node_modules/bin-wrapper/node_modules/download/node_modules']
npm ERR! error rolling back   errno: 53,
npm ERR! error rolling back   code: 'ENOTEMPTY',
npm ERR! error rolling back   path: '/home/pete/Sites/fe-skeleton/node_modules/grunt-contrib-imagemin/node_modules/imagemin/node_modules/imagemin-gifsicle/node_modules/gifsicle/node_modules/bin-wrapper/node_modules/download/node_modules' }
npm ERR! Error: ENOENT, lstat '/home/pete/Sites/fe-skeleton/node_modules/grunt-contrib-imagemin/node_modules/imagemin/node_modules/imagemin-gifsicle/node_modules/gifsicle/node_modules/bin-wrapper/node_modules/download/node_modules/request/node_modules/combined-stream/lib/combined_stream.js'
npm ERR! If you need help, you may report this log at:
npm ERR!     <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR!     <[email protected]>

npm ERR! System Linux 3.13.0-44-generic
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "install"
npm ERR! cwd /home/pete/Sites/fe-skeleton
npm ERR! node -v v0.10.25
npm ERR! npm -v 1.3.10
npm ERR! path /home/pete/Sites/fe-skeleton/node_modules/grunt-contrib-imagemin/node_modules/imagemin/node_modules/imagemin-gifsicle/node_modules/gifsicle/node_modules/bin-wrapper/node_modules/download/node_modules/request/node_modules/combined-stream/lib/combined_stream.js
npm ERR! fstream_path /home/pete/Sites/fe-skeleton/node_modules/grunt-contrib-imagemin/node_modules/imagemin/node_modules/imagemin-gifsicle/node_modules/gifsicle/node_modules/bin-wrapper/node_modules/download/node_modules/request/node_modules/combined-stream/lib/combined_stream.js
npm ERR! fstream_type File
npm ERR! fstream_class FileWriter
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR! fstream_stack /usr/lib/nodejs/fstream/lib/writer.js:284:26
npm ERR! fstream_stack Object.oncomplete (fs.js:107:15)
npm ERR! Error: ENOENT, lstat '/home/pete/Sites/fe-skeleton/node_modules/grunt-contrib-imagemin/node_modules/imagemin/node_modules/imagemin-gifsicle/node_modules/gifsicle/node_modules/bin-wrapper/node_modules/download/node_modules/request/node_modules/caseless/index.js'
npm ERR! If you need help, you may report this log at:
npm ERR!     <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR!     <[email protected]>

npm ERR! System Linux 3.13.0-44-generic
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "install"
npm ERR! cwd /home/pete/Sites/fe-skeleton
npm ERR! node -v v0.10.25
npm ERR! npm -v 1.3.10
npm ERR! path /home/pete/Sites/fe-skeleton/node_modules/grunt-contrib-imagemin/node_modules/imagemin/node_modules/imagemin-gifsicle/node_modules/gifsicle/node_modules/bin-wrapper/node_modules/download/node_modules/request/node_modules/caseless/index.js
npm ERR! fstream_path /home/pete/Sites/fe-skeleton/node_modules/grunt-contrib-imagemin/node_modules/imagemin/node_modules/imagemin-gifsicle/node_modules/gifsicle/node_modules/bin-wrapper/node_modules/download/node_modules/request/node_modules/caseless/index.js
npm ERR! fstream_type File
npm ERR! fstream_class FileWriter
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR! fstream_stack /usr/lib/nodejs/fstream/lib/writer.js:284:26
npm ERR! fstream_stack Object.oncomplete (fs.js:107:15)
npm ERR! Error: ENOENT, lstat '/home/pete/Sites/fe-skeleton/node_modules/grunt-contrib-imagemin/node_modules/imagemin/node_modules/imagemin-gifsicle/node_modules/gifsicle/node_modules/bin-build/node_modules/download/node_modules/request/request.js'
npm ERR! If you need help, you may report this log at:
npm ERR!     <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR!     <[email protected]>

npm ERR! System Linux 3.13.0-44-generic
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "install"
npm ERR! cwd /home/pete/Sites/fe-skeleton
npm ERR! node -v v0.10.25
npm ERR! npm -v 1.3.10
npm ERR! path /home/pete/Sites/fe-skeleton/node_modules/grunt-contrib-imagemin/node_modules/imagemin/node_modules/imagemin-gifsicle/node_modules/gifsicle/node_modules/bin-build/node_modules/download/node_modules/request/request.js
npm ERR! fstream_path /home/pete/Sites/fe-skeleton/node_modules/grunt-contrib-imagemin/node_modules/imagemin/node_modules/imagemin-gifsicle/node_modules/gifsicle/node_modules/bin-build/node_modules/download/node_modules/request/request.js
npm ERR! fstream_type File
npm ERR! fstream_class FileWriter
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR! fstream_stack /usr/lib/nodejs/fstream/lib/writer.js:284:26
npm ERR! fstream_stack Object.oncomplete (fs.js:107:15)
npm ERR! error rolling back Error: ENOTEMPTY, rmdir '/home/pete/Sites/fe-skeleton/node_modules/grunt-contrib-imagemin/node_modules/imagemin/node_modules/imagemin-gifsicle/node_modules/gifsicle/node_modules/bin-wrapper/node_modules/download/node_modules/request/node_modules'
npm ERR! error rolling back  [email protected] { [Error: ENOTEMPTY, rmdir '/home/pete/Sites/fe-skeleton/node_modules/grunt-contrib-imagemin/node_modules/imagemin/node_modules/imagemin-gifsicle/node_modules/gifsicle/node_modules/bin-wrapper/node_modules/download/node_modules/request/node_modules']
npm ERR! error rolling back   errno: 53,
npm ERR! error rolling back   code: 'ENOTEMPTY',
npm ERR! error rolling back   path: '/home/pete/Sites/fe-skeleton/node_modules/grunt-contrib-imagemin/node_modules/imagemin/node_modules/imagemin-gifsicle/node_modules/gifsicle/node_modules/bin-wrapper/node_modules/download/node_modules/request/node_modules' }
npm ERR! Error: ENOENT, chmod '/home/pete/Sites/fe-skeleton/node_modules/grunt-contrib-imagemin/node_modules/imagemin/node_modules/imagemin-gifsicle/node_modules/gifsicle/node_modules/bin-build/node_modules/download/node_modules/decompress-unzip/node_modules/adm-zip/methods/index.js'
npm ERR! If you need help, you may report this log at:
npm ERR!     <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR!     <[email protected]>

npm ERR! System Linux 3.13.0-44-generic
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "install"
npm ERR! cwd /home/pete/Sites/fe-skeleton
npm ERR! node -v v0.10.25
npm ERR! npm -v 1.3.10
npm ERR! path /home/pete/Sites/fe-skeleton/node_modules/grunt-contrib-imagemin/node_modules/imagemin/node_modules/imagemin-gifsicle/node_modules/gifsicle/node_modules/bin-build/node_modules/download/node_modules/decompress-unzip/node_modules/adm-zip/methods/index.js
npm ERR! fstream_path /home/pete/Sites/fe-skeleton/node_modules/grunt-contrib-imagemin/node_modules/imagemin/node_modules/imagemin-gifsicle/node_modules/gifsicle/node_modules/bin-build/node_modules/download/node_modules/decompress-unzip/node_modules/adm-zip/methods/index.js
npm ERR! fstream_type File
npm ERR! fstream_class FileWriter
npm ERR! fstream_finish_call chmod
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR! fstream_stack /usr/lib/nodejs/fstream/lib/writer.js:305:19
npm ERR! fstream_stack Object.oncomplete (fs.js:107:15)
npm ERR! Error: ENOENT, utime '/home/pete/Sites/fe-skeleton/node_modules/grunt-contrib-imagemin/node_modules/imagemin/node_modules/imagemin-gifsicle/node_modules/gifsicle/node_modules/bin-wrapper/node_modules/download/node_modules/request/node_modules/oauth-sign/LICENSE'
npm ERR! If you need help, you may report this log at:
npm ERR!     <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR!     <[email protected]>

npm ERR! System Linux 3.13.0-44-generic
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "install"
npm ERR! cwd /home/pete/Sites/fe-skeleton
npm ERR! node -v v0.10.25
npm ERR! npm -v 1.3.10
npm ERR! path /home/pete/Sites/fe-skeleton/node_modules/grunt-contrib-imagemin/node_modules/imagemin/node_modules/imagemin-gifsicle/node_modules/gifsicle/node_modules/bin-wrapper/node_modules/download/node_modules/request/node_modules/oauth-sign/LICENSE
npm ERR! fstream_path /home/pete/Sites/fe-skeleton/node_modules/grunt-contrib-imagemin/node_modules/imagemin/node_modules/imagemin-gifsicle/node_modules/gifsicle/node_modules/bin-wrapper/node_modules/download/node_modules/request/node_modules/oauth-sign/LICENSE
npm ERR! fstream_type File
npm ERR! fstream_class FileWriter
npm ERR! fstream_finish_call utimes
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR! fstream_stack /usr/lib/nodejs/fstream/lib/writer.js:305:19
npm ERR! fstream_stack Object.oncomplete (fs.js:107:15)
npm ERR! Error: ENOENT, lstat '/home/pete/Sites/fe-skeleton/node_modules/grunt-contrib-imagemin/node_modules/imagemin/node_modules/imagemin-gifsicle/node_modules/gifsicle/node_modules/bin-wrapper/node_modules/download/node_modules/request/node_modules/forever-agent/package.json'
npm ERR! If you need help, you may report this log at:
npm ERR!     <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR!     <[email protected]>

npm ERR! System Linux 3.13.0-44-generic
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "install"
npm ERR! cwd /home/pete/Sites/fe-skeleton
npm ERR! node -v v0.10.25
npm ERR! npm -v 1.3.10
npm ERR! path /home/pete/Sites/fe-skeleton/node_modules/grunt-contrib-imagemin/node_modules/imagemin/node_modules/imagemin-gifsicle/node_modules/gifsicle/node_modules/bin-wrapper/node_modules/download/node_modules/request/node_modules/forever-agent/package.json
npm ERR! fstream_path /home/pete/Sites/fe-skeleton/node_modules/grunt-contrib-imagemin/node_modules/imagemin/node_modules/imagemin-gifsicle/node_modules/gifsicle/node_modules/bin-wrapper/node_modules/download/node_modules/request/node_modules/forever-agent/package.json
npm ERR! fstream_type File
npm ERR! fstream_class FileWriter
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR! fstream_stack /usr/lib/nodejs/fstream/lib/writer.js:284:26
npm ERR! fstream_stack Object.oncomplete (fs.js:107:15)
npm ERR! Error: ENOENT, open '/home/pete/Sites/fe-skeleton/node_modules/grunt-contrib-imagemin/node_modules/imagemin/node_modules/imagemin-gifsicle/node_modules/gifsicle/node_modules/bin-wrapper/node_modules/download/node_modules/request/node_modules/mime-types/README.md'
npm ERR! If you need help, you may report this log at:
npm ERR!     <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR!     <[email protected]>

npm ERR! System Linux 3.13.0-44-generic
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "install"
npm ERR! cwd /home/pete/Sites/fe-skeleton
npm ERR! node -v v0.10.25
npm ERR! npm -v 1.3.10
npm ERR! path /home/pete/Sites/fe-skeleton/node_modules/grunt-contrib-imagemin/node_modules/imagemin/node_modules/imagemin-gifsicle/node_modules/gifsicle/node_modules/bin-wrapper/node_modules/download/node_modules/request/node_modules/mime-types/README.md
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR! error rolling back Error: ENOTEMPTY, rmdir '/home/pete/Sites/fe-skeleton/node_modules/grunt-contrib-imagemin/node_modules/imagemin/node_modules/imagemin-gifsicle/node_modules/gifsicle/node_modules/bin-wrapper/node_modules/download/node_modules/request/node_modules'
npm ERR! error rolling back  [email protected] { [Error: ENOTEMPTY, rmdir '/home/pete/Sites/fe-skeleton/node_modules/grunt-contrib-imagemin/node_modules/imagemin/node_modules/imagemin-gifsicle/node_modules/gifsicle/node_modules/bin-wrapper/node_modules/download/node_modules/request/node_modules']
npm ERR! error rolling back   errno: 53,
npm ERR! error rolling back   code: 'ENOTEMPTY',
npm ERR! error rolling back   path: '/home/pete/Sites/fe-skeleton/node_modules/grunt-contrib-imagemin/node_modules/imagemin/node_modules/imagemin-gifsicle/node_modules/gifsicle/node_modules/bin-wrapper/node_modules/download/node_modules/request/node_modules' }
npm WARN optional dep failed, continuing [email protected]
npm ERR! Error: ENOENT, open '/home/pete/Sites/fe-skeleton/node_modules/grunt-contrib-imagemin/node_modules/imagemin/node_modules/imagemin-gifsicle/node_modules/gifsicle/node_modules/bin-wrapper/node_modules/download/node_modules/request/node_modules/json-stringify-safe/package.json'
npm ERR! If you need help, you may report this log at:
npm ERR!     <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR!     <[email protected]>

npm ERR! System Linux 3.13.0-44-generic
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "install"
npm ERR! cwd /home/pete/Sites/fe-skeleton
npm ERR! node -v v0.10.25
npm ERR! npm -v 1.3.10
npm ERR! path /home/pete/Sites/fe-skeleton/node_modules/grunt-contrib-imagemin/node_modules/imagemin/node_modules/imagemin-gifsicle/node_modules/gifsicle/node_modules/bin-wrapper/node_modules/download/node_modules/request/node_modules/json-stringify-safe/package.json
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR! error rolling back Error: ENOTEMPTY, rmdir '/home/pete/Sites/fe-skeleton/node_modules/grunt-contrib-imagemin/node_modules/imagemin/node_modules/imagemin-gifsicle/node_modules/gifsicle/node_modules/bin-wrapper/node_modules/download/node_modules/request/node_modules/form-data'
npm ERR! error rolling back  [email protected] { [Error: ENOTEMPTY, rmdir '/home/pete/Sites/fe-skeleton/node_modules/grunt-contrib-imagemin/node_modules/imagemin/node_modules/imagemin-gifsicle/node_modules/gifsicle/node_modules/bin-wrapper/node_modules/download/node_modules/request/node_modules/form-data']
npm ERR! error rolling back   errno: 53,
npm ERR! error rolling back   code: 'ENOTEMPTY',
npm ERR! error rolling back   path: '/home/pete/Sites/fe-skeleton/node_modules/grunt-contrib-imagemin/node_modules/imagemin/node_modules/imagemin-gifsicle/node_modules/gifsicle/node_modules/bin-wrapper/node_modules/download/node_modules/request/node_modules/form-data' }
/bin/sh: 1: node: not found
gyp: Call to 'node -e "require('nan')"' returned exit status 127. while trying to load binding.gyp
gyp ERR! configure error 
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onCpExit (/usr/share/node-gyp/lib/configure.js:431:16)
gyp ERR! stack     at ChildProcess.EventEmitter.emit (events.js:98:17)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:797:12)
gyp ERR! System Linux 3.13.0-44-generic
gyp ERR! command "nodejs" "/usr/bin/node-gyp" "configure" "build"
gyp ERR! cwd /home/pete/Sites/fe-skeleton/node_modules/grunt-contrib-imagemin/node_modules/imagemin/node_modules/imagemin-jpegtran/node_modules/jpegtran-bin/node_modules/bin-wrapper/node_modules/download/node_modules/decompress-unzip/node_modules/adm-zip/node_modules/fidonet-mailer-binkp-crypt
gyp ERR! node -v v0.10.25
gyp ERR! node-gyp -v v0.10.10
gyp ERR! not ok 
npm WARN This failure might be due to the use of legacy binary "node"
npm WARN For further explanations, please read
/usr/share/doc/nodejs/README.Debian


npm http 304 https://registry.npmjs.org/nan
/bin/sh: 1: node: not found
gyp: Call to 'node -e "require('nan')"' returned exit status 127. while trying to load binding.gyp
gyp ERR! configure error 
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onCpExit (/usr/share/node-gyp/lib/configure.js:431:16)
gyp ERR! stack     at ChildProcess.EventEmitter.emit (events.js:98:17)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:797:12)
gyp ERR! System Linux 3.13.0-44-generic
gyp ERR! command "nodejs" "/usr/bin/node-gyp" "configure" "build"
gyp ERR! cwd /home/pete/Sites/fe-skeleton/node_modules/grunt-contrib-imagemin/node_modules/imagemin/node_modules/imagemin-pngquant/node_modules/pngquant-bin/node_modules/bin-wrapper/node_modules/download/node_modules/decompress-unzip/node_modules/adm-zip/node_modules/fidonet-mailer-binkp-crypt
gyp ERR! node -v v0.10.25
gyp ERR! node-gyp -v v0.10.10
gyp ERR! not ok 
npm WARN This failure might be due to the use of legacy binary "node"
npm WARN For further explanations, please read
/usr/share/doc/nodejs/README.Debian

/bin/sh: 1: node: not found
gyp: Call to 'node -e "require('nan')"' returned exit status 127. while trying to load binding.gyp
gyp ERR! configure error 
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onCpExit (/usr/share/node-gyp/lib/configure.js:431:16)
gyp ERR! stack     at ChildProcess.EventEmitter.emit (events.js:98:17)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:797:12)
gyp ERR! System Linux 3.13.0-44-generic
gyp ERR! command "nodejs" "/usr/bin/node-gyp" "configure" "build"
gyp ERR! cwd /home/pete/Sites/fe-skeleton/node_modules/grunt-contrib-imagemin/node_modules/imagemin/node_modules/imagemin-optipng/node_modules/optipng-bin/node_modules/bin-wrapper/node_modules/download/node_modules/decompress-unzip/node_modules/adm-zip/node_modules/fidonet-mailer-binkp-crypt
gyp ERR! node -v v0.10.25
gyp ERR! node-gyp -v v0.10.10
gyp ERR! not ok 
npm WARN This failure might be due to the use of legacy binary "node"
npm WARN For further explanations, please read
/usr/share/doc/nodejs/README.Debian

Some of my environment stats:

$ ruby -v
ruby 2.1.5p273 (2014-11-13 revision 48405) [x86_64-linux]
$ npm -v
1.3.10

Use Webpack as module system, compiler and minifier

Webpack has been tested enough internally to be roadworthy at this point. It will handle our CommonJS bundling (with the much-needed multi-bundling included), our CSS and JS compilation and uglifying.

We can remove a lot of the devDependencies in package.json with this, including Browserify and our CSS/JS deps, and get the bloat down.

Update docker build to user generic automated build container from docker hub

We have a generic container available on docker hub now, we should use this for docker-based building. This container is built from source on http://github.com/rehabstudio/dockerfiles

README mentions multiple task runners

With grunt support removed, should the section about removing dependencies of other task runners be stripped as well?

Add Dockerfile for deployment to rehab-labs

Will help with quick setup and prototyping, Hack Weeks, Triage work, etc.

Test Suite: Code Formatting.

On projects such as Miyagi it's become very important for us to ensure our files are linted and formatted as intended. We've plugged the linter into our gulp test command and very shortly will be plugging in JSCS also. This is a reminder for myself to build this capability back into the skeleton.

Remove testing modules/structure

Move the testing stuff (Karma et al) out of the default setup. They're an optional extra for now.

Creating a rehab-testing NPM module which we could optionally install would be an elegant solution for including them where needed.

Simplify configuration file setup

The current system of having configuration inside the /run subdirectories isn't floating a lot of boats internally.

My take on it is: a skeleton user shouldn't have to dig into the task directories at all when setting up the project. The config should live either entirely in the run dir, or entirely in the root, in a single config file. Happy to have this discussed and looked at from many different angles, but the config should all live in one place, in my opinion.

Remove grunt

We've moved past the need for grunt in any new build we do. I think we can do away with the shared tasks and greatly simplify the /run directory now.

[to-do] Cloning

Need a segment in the docs for cloning the repo, if its to be the base of a project. Also information on how to change a repositories url and safely remove fe-skeletons maybe beneficial for those not in the know.

Sourcetree doesn't show the jsLint error commit

If you use terminal, git commit will give you the Lint error associated that prevent your commit. SourceTree will throw just a generic error. Is there a way to log the error in Sourcetree as well ?

make watch returning funky error

Seems to be something with es6 promise in the styles command

Ruby sass version ( Sass 3.4.6 (Selective Steve) )

➜  static git:(develop) make watch
gulp;
 - Loading module styles
 - Loading module scripts
 - Loading module build
 - Loading module default
[14:51:19] Using gulpfile ~/sites/planner-2.0/app/apps/triage/static/gulpfile.js
[14:51:19] Starting 'default'...
[14:51:19] Starting 'styles'...
[14:51:19] Starting 'scripts'...
[14:51:19] Finished 'default' after 7.44 ms
[14:51:19] 'styles' errored after 8.05 ms
[14:51:19] Error: Something went wrong.
    at formatError (/usr/local/lib/node_modules/gulp/bin/gulp.js:161:10)
    at Gulp.<anonymous> (/usr/local/lib/node_modules/gulp/bin/gulp.js:187:15)
    at Gulp.emit (events.js:95:17)
    at Gulp.Orchestrator._emitTaskDone (/Users/chris/sites/planner-2.0/app/apps/triage/static/node_modules/gulp/node_modules/orchestrator/index.js:264:8)
    at /Users/chris/sites/planner-2.0/app/apps/triage/static/node_modules/gulp/node_modules/orchestrator/index.js:275:23
    at finish (/Users/chris/sites/planner-2.0/app/apps/triage/static/node_modules/gulp/node_modules/orchestrator/lib/runTask.js:21:8)
    at cb (/Users/chris/sites/planner-2.0/app/apps/triage/static/node_modules/gulp/node_modules/orchestrator/lib/runTask.js:29:3)
    at /Users/chris/sites/planner-2.0/app/apps/triage/static/run/tasks/styles/gulp.js:38:13
    at $$$internal$$tryCatch (/Users/chris/sites/planner-2.0/app/apps/triage/static/node_modules/es6-promise/dist/es6-promise.js:304:16)
    at $$$internal$$invokeCallback (/Users/chris/sites/planner-2.0/app/apps/triage/static/node_modules/es6-promise/dist/es6-promise.js:316:17)
[14:51:19] Finished 'scripts' after 11 ms

Convert JSCS rules to ESLint rules.

JSCS is soon to be absorbed fully by the ESLint team. Whenever this happens we should port all of our JSCS rules over to ESLint then delete the JSCS task.

There is nothing to action currently, this issue is just a reminder for future reference to look into this.

Update README with information on using optional docker-based builds

Scripts task takes a lengthy time, whereas Karmas bundling is a fraction of the time

The scripts task is taking far too long to build the bundle and complete the task. We'll need to debug and see where the overhead is happening.

Remove the gorgonic docker conditional code from Makefile

The docker code to determine and reuse containers in the Makefile is a beast that should never have seen the light of day. This is issue is to remind myself to remove and simplify this creature, with a single simple docker-compose.yml and a very small number of short readable Makefile rules.

Updated .gitignore, seems old and maybe redundant

Best to use an auto generated one from gitignore.io or similar, with our specific additions on top

Plans for implementing JS style checking?

I came across this today and thought it might be a good thing to include into the toolchain. The only downside I can think of is that it might be time consuming for us to write the rules we require.

JSCS:
http://jscs.info/overview.html

Reduce gulp task structure complexity

With the removal of alternate task runners, do each of the gulp tasks require the _common.js/gulp.js duo, wouldn't this be simpler to replace with one file per task.

run/tasks/scripts/
...  _common.js
...  gulp.js
run/tasks/styles/
...  _common.js
...  gulp.js

becomes

run/tasks/scripts.js
run/tasks/styles.js

Default gulp task does not perform build

The default gulp task activates the watchers but performs no build steps (at least until you save a file).

I think the default task should be to run a full build and exit. gulp watch should be an explicit task that the developer must manually activate. The idea being that one could pull the repo, run npm install then gulp, and have the application in a runnable state.

Will PR this later in the week, just putting this here for reference.

Add info in readme on bundle definitions for `styles` and `scripts`

For someone unfamiliar with the process it'd be nice to tell them that their code needs to be defined as bundles in <task>/_common.js before it will be compiled.

Add a step-by-step how-to guide

From git pull to browser loading, a step-by-step would be nice to have.

Update ruby sass for libsass

Whenever libsass is stable.

Need further checks on `server` and `build`.

build should alert the user if there is no CSS or JS bundles specified to move.

server should alert the user if there is no dist directory to host.

Both should output warning to the terminal using chalk (gray text upon yellow background).

Docker no longer needs ruby and sass gem as dependencies.

Reduce build pipeline complexity... again :)

Discussed before in #39 I think this can be revisited. My original suggestion in #39 of one file per task and not one folder + one file per tasks like we have now would be an improvement. But having a look at the skeleton as it stands...

There are a grand total of 227 lines in 13 files nested 3 deep in 11 folders, this seems an unnecessarily complex tree for a reasonable number of lines that could be easily be maintained and still readily understood in a single file. In fact the number of lines is like to decrease by 3 or 4 per file, as duplicate requires would be removed, and we would not need the rather esoteric auto folder loading that is at the route of the structure.

I'd estimate less than 180 lines in the resulting file, meaning you could add at least 20 more lines of comments (if necessary) to maintain readability and still be a manageable file length.

I will PR a suggested solution here once time permits, but before that I'm happy to hear arguments for and against.

Static/template HTML output in dist?

If this skeleton was pulled for a static prototype (say, something to be FTP'd up to some webspace for testing), there is currently no handling for HTML. Maybe a templates or html folder that gets copied to dist might be an idea?

Should RequireJS support be removed?

Given that we are going to be looking toward webpack for our bundling needs in the near future, I don't see anyone going back to RequireJS anytime soon (I never thought I'd say that).

Removing it would:

Simplify the watch method
Remove the entire need for the templates method (as Browserify does this for us via hbsfy).
Simplify the test suites configuration.
Remove the need for five or more packages from package.json.

Recommend Projects

React

A declarative, efficient, and flexible JavaScript library for building user interfaces.
Vue.js

🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript

TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
TensorFlow

An Open Source Machine Learning Framework for Everyone
Django

The Web framework for perfectionists with deadlines.
Laravel

A PHP framework for web artisans
D3

Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

javascript

JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
web

Some thing interesting about web. New door for the world.
server

A server is a program made to process requests and deliver data to clients.
Machine learning

Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Visualization

Some thing interesting about visualization, use data art
Game

Some thing interesting about game, make everyone happy.

Recommend Org

Facebook

We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft

Open source projects and samples from Microsoft.
Google

Google ❤️ Open Source for everyone.
Alibaba

Alibaba Open Source for everyone
D3

Data-Driven Documents codes.
Tencent

China tencent open source team.