Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

no tasks were found [win 8.1 64] #79

Closed
alubbe opened this issue Jan 9, 2015 · 9 comments
Closed

no tasks were found [win 8.1 64] #79

alubbe opened this issue Jan 9, 2015 · 9 comments

Comments

@alubbe
Copy link
Contributor

alubbe commented Jan 9, 2015

I've been trying to set up the sequelize-cli but to no avail. As a note, the "old" cli that comes with sequelize@1.7.10 works.

These steps

mkdir tmp
cd .\tmp
npm install sequelize sequelize-cli mysql
.\node_modules\.bin\sequelize init

yield

Sequelize [Node: 0.11.13, CLI: 1.0.2, ORM: 2.0.0-rc7]

[14:56:47] Using sequelizefile C:\GitHub\tmp\node_modules\sequelize-cli\lib\sequelizefile.js
[14:56:47] Task 'init' was not defined in your sequelizefile but you tried to run it.
[14:56:47] Please check the documentation for proper sequelizefile formatting.

I do not have a global installation of this or the previous cli. No tasks, not even the default task, are found and can be run.

This bug applies to 1.0.2, 1.0.0 and 0.3.3.

@sdepold
Copy link
Member

sdepold commented Jan 9, 2015

Oh you are using node 0.11. Hm not sure if the CLI is compatible with that. Its most likely not. Let me check.

@sdepold
Copy link
Member

sdepold commented Jan 9, 2015

Hm works on OS X. Let me spin up my windows machine

@sdepold
Copy link
Member

sdepold commented Jan 9, 2015

alright. does not work :(

@sdepold
Copy link
Member

sdepold commented Jan 9, 2015

This issue related to gulpjs/gulp#664

@sdepold
Copy link
Member

sdepold commented Jan 9, 2015

And this browserify/resolve#61

@sdepold
Copy link
Member

sdepold commented Jan 9, 2015

You probably want to consider using the current stable version of nodejs

@alubbe
Copy link
Contributor Author

alubbe commented Jan 9, 2015

this is really unfortunate :(
thanks for tracking it down, I will see if I can get a version manager to work on this machine.

that means my main code will continue to run in 0.11, while my migration tasks run 0.10 - oh joy.
should we alert the iojs team to this as well?

@alubbe alubbe closed this as completed Jan 9, 2015
@alubbe alubbe reopened this Jan 9, 2015
@alubbe
Copy link
Contributor Author

alubbe commented Jan 15, 2015

Okay, I can confirm that this is now fixed in io.js.

@alubbe alubbe closed this as completed Jan 15, 2015
@sdepold
Copy link
Member

sdepold commented Jan 15, 2015

great :)

codetriage-readme-bot pushed a commit to codetriage-readme-bot/cli that referenced this issue Jun 5, 2019
[Low priority] Tweak dev setup to clone via https
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants