Skip to content
This repository has been archived by the owner on Aug 30, 2021. It is now read-only.

Enhancement: Deprecating Grunt in favor of Gulp and NPM commands #1390

Merged
merged 2 commits into from
Jul 13, 2016

Conversation

lirantal
Copy link
Member

feat(gulp): updating the README.md instructions with the changes to gulp being the mainstream vs the deprecation of grunt. Also added gulp as a task runner for freely executing tasks through running npm commands

Follow-up for #1296

…ulp being the mainstream vs the deprecation of grunt. Also added gulp as a task runner for freely executing tasks through Lifecycle scripts included in meanjs:

  start
    gulp
  test
    gulp test
  postinstall
    bower install --allow-root && bower prune --allow-root

available via `npm run-script`:
  update
    npm update && npm prune && bower install --allow-root && bower prune --allow-root
  start:prod
    gulp prod
  start:debug
    gulp debug
  gulp
    gulp
  lint
    gulp lint
  test:server
    gulp test:server
  test:client
    gulp test:client
  test:e2e
    gulp test:e2e
  test:watch
    gulp test:server:watch
  test:watch:onlyChanged
    gulp test:server:watch --onlyChanged
  generate-ssl-certs
    scripts/generate-ssl-certs.sh commands
@lirantal
Copy link
Member Author

@codydaig @mleanos @simison there we go. can you please review?

@coveralls
Copy link

coveralls commented Jul 11, 2016

Coverage Status

Coverage remained the same at 69.714% when pulling 0b055cb on lirantal:feat/readme-npm-update-gulp-scripts into a7370a7 on meanjs:master.

@@ -91,12 +95,13 @@ That's it! Your application should be running. To proceed with your development,
If you encounter any problems, try the Troubleshooting section.

* explore `config/env/development.js` for development environment configuration options
* it is possible to
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this line seems out of place?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, I just forgot to actually end that text... I wanted to refer to @mleanos 's comment about doing 'npm run gulp ' - checkout the updated PR.

@codydaig
Copy link
Member

@lirantal Overall looks good, just one line that seems out of place to me.

```
It will try to seed the users 'user' and 'admin'. If one of the user already exists, it will display an error message on the console. Just grab the passwords from the console.

In Production:
```bash
MONGO_SEED=true grunt prod
MONGO_SEED=true npm start:prod
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This may be out of the scope of this PR, but I feel that the MONGO_SEED option here is a bit confusing. I think we could just move the seeding option to it's own section.

@mleanos
Copy link
Member

mleanos commented Jul 11, 2016

LGTM (other than what Cody pointed out). Also, my comment isn't that much of a priority, and can be addressed in a separate PR if need be.

@lirantal
Copy link
Member Author

@codydaig @mleanos check out the updated README, I updated the broken text to:

  • it is possible to run any gulp tasks using npm's run command, for example: npm run gulp test:server:watch

@coveralls
Copy link

coveralls commented Jul 12, 2016

Coverage Status

Coverage remained the same at 69.714% when pulling f76c75a on lirantal:feat/readme-npm-update-gulp-scripts into a7370a7 on meanjs:master.

@codydaig
Copy link
Member

LGTM

1 similar comment
@mleanos
Copy link
Member

mleanos commented Jul 13, 2016

LGTM

@lirantal
Copy link
Member Author

Thanks 👍

@lirantal lirantal merged commit d915157 into meanjs:master Jul 13, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants