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

package.json has the wrong start #8

Closed
baer opened this issue Nov 5, 2014 · 2 comments
Closed

package.json has the wrong start #8

baer opened this issue Nov 5, 2014 · 2 comments

Comments

@baer
Copy link
Collaborator

baer commented Nov 5, 2014

npm start will call gulp help

https://github.com/divmain/js-seed/blob/master/package.json#L53

https://github.com/divmain/js-seed/blob/master/gulpfile.js#L22-L24

@divmain
Copy link
Owner

divmain commented Nov 6, 2014

Hmm... it's not clear to me what npm start should do in this context. Since (for now) this is a FE-only application, there really isn't anything to start, except maybe a build. But even that doesn't seem a natural fit to me.

@baer
Copy link
Collaborator Author

baer commented Nov 6, 2014

Good point, maybe npm start should be removed until there is a server side thing to start.

divmain added a commit that referenced this issue Nov 20, 2014
…ages

* origin/master:
  switch to YAML syntax for .eslintrc and add documentation
  Clean directory contents without removing the directory
  Correct merge conflict where composite didn't get converted to new gulp format
  Use require-dir to pull in tasks automatically
  remove npm start since it really doesn't do anything, closes #8
  Add license to the project
  Add travis.yml file
  Add a .editorconfig file
  Update index.html to follow html5 Boilerplate

Conflicts:
	package.json
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants