Giter VIP home page Giter VIP logo

machinepack-sailsgulpify's Introduction

node-machine logo machinepack-sailsgulpify

Add toggle ability to choose gulp or grunt as task runner on create new

Installation   NPM version Build Status

$ npm install machinepack-sailsgulpify

Usage

For the latest usage documentation, version information, and test status of this module, see http://node-machine.org/machinepack-sailsgulpify. The generated manpages for each machine contain a complete reference of all expected inputs, possible exit states, and example return values. If you need more help, or find a bug, jump into Gitter or leave a message in the project newsgroup. To configure, run

npm install machinepack-prompts
node node_modules/machinepack-sailsgulpify/templates/toggleEngine.js

at the prompt, enter gulpifysails for install. To toggle between gulp and grunt, use gulp or grunt instead of gulpifysails with toggleEngine.js

Todo

Find a way to move the toggleEngine.js to teh root of the project on machinepack install.

This is a machinepack, an NPM module which exposes a set of related Node.js machines according to the machinepack specification. Documentation pages for the machines contained in this module (as well as all other NPM-hosted machines for Node.js) are automatically generated and kept up-to-date on the public registry. Learn more at http://node-machine.org/implementing/FAQ.

License

MIT © 2015 contributors

machinepack-sailsgulpify's People

Contributors

jeremy-albuixech avatar joshdobbin avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar

machinepack-sailsgulpify's Issues

This machinepack does not remove the need for grunt entirely.

After going through the install and setup process you'd think that the need for grunt as a dependency is removed but it seems that grunt is still needed somewhere in the deep bowels of the project.
Let me explain, after installing this plugin I went for removing grunt from package.json, I have also removed all of grunt modules in node_modules folder, deleted the tasks folder (grunt tasks) and removed gruntfile.js.
However, when I lift the project it starts seemingly ok but a quick look at the browser console reveals a couple of 404s, it looks like gulp hasn't compiled importer.less and failed to copy it and sails.io.js.
Because this is a fresh install the project doesn't contain any other assets (which wouldn't be copied either I presume).
The other strange thing which is likely the root cause of the problem, is that whereas grunt used to copy all needed public assets to .temp/public/, this new gulp setup is not doing that and I wonder where is the site being served from?

There is a clear dependency on grunt after installing and configuring the project to use this plugin.

[Feature request] A way to modify `sails new` behaviour

It would be nice, like with the old generator, if we could configure this machinepack to run when we are crating a new project, and let it set up gulp from the beginning, so we don't have to install the machinepack locally to every project after it's creation.

If there is such a way, then it needs to be added to the usage section in the readme.

Livereload causes crash on any change

After follow install instructions and running gulp at the command line, any file change results in the following:

/Users/austinmao/Sites/sails-mongoose-boilerplate/tasks-gulp/config/watch.js:19
                    server.changed(file.path);
                           ^

TypeError: server.changed is not a function
  at EventEmitter.<anonymous> (/Users/austinmao/Sites/sails-mongoose-boilerplate/tasks-gulp/config/watch.js:19:13)
  at emitOne (events.js:77:13)
  at EventEmitter.emit (events.js:169:7)
  at Gaze.<anonymous> (/Users/austinmao/Sites/sails-mongoose-boilerplate/node_modules/gulp/node_modules/vinyl-fs/node_modules/glob-watcher/index.js:17:11)
  at emitTwo (events.js:87:13)
  at Gaze.emit (events.js:172:7)
  at Gaze.emit (/Users/austinmao/Sites/sails-mongoose-boilerplate/node_modules/gulp/node_modules/vinyl-fs/node_modules/glob-watcher/node_modules/gaze/lib/gaze.js:129:32)
  at /Users/austinmao/Sites/sails-mongoose-boilerplate/node_modules/gulp/node_modules/vinyl-fs/node_modules/glob-watcher/node_modules/gaze/lib/gaze.js:415:16
  at StatWatcher._pollers.(anonymous function) (/Users/austinmao/Sites/sails-mongoose-boilerplate/node_modules/gulp/node_modules/vinyl-fs/node_modules/glob-watcher/node_modules/gaze/lib/gaze.js:326:7)
  at emitTwo (events.js:87:13)
  at StatWatcher.emit (events.js:172:7)
  at StatWatcher._handle.onchange (fs.js:1291:10)

How to install

Hey, reading over the documentation on here, NPM, and Node Machine, never really understand how this is supposed to work. Are you supposed to run a sails new projectName and then hook this machinepack in somehow? Or is there and independent command to run and generate a sails app with included Gulp compilation (like `gulpifysails new projectName)? Not really sure how to use this tool and it's never really explained just kind of assumed that the user should know how this is supposed to work.

Sass task

Hi, I would like an sass task for this repo to easy make an switch to scss :)

refactor machinepack for updating sails

when saisl is updated in project, changes made by gulpifysails get lost. When running node node_modules/machinepack-sailsgulpify/templates/toggleEngine.js after an upgrade, it reinstall all modules. We need a toggle for package install so that if we have updated modules and upgrade sails, all we need to do is recreate the gulp linkage.

Documentation clarity

This is going to sound like a stupid question, but I need a little help with getting this up and running. Where should I install the machinepack? I followed the instructions in a test directory but sails new still generates a site using grunt. Any help would be much appreciated!

Recommend Projects

  • React photo React

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

  • Vue.js photo Vue.js

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

  • Typescript photo Typescript

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

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo 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.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

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

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.