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

Upgrading to 0.6.6 lock issues #34

Closed
wbashir opened this issue Oct 20, 2013 · 7 comments
Closed

Upgrading to 0.6.6 lock issues #34

wbashir opened this issue Oct 20, 2013 · 7 comments

Comments

@wbashir
Copy link

wbashir commented Oct 20, 2013

I just upgraded to the latest version of both Meteor and this plugin (0.3.1). When i attempt to run my application, i get an error.

npm ERR! missing: demeteorizer@*, required by undefined@undefined
npm ERR! not ok code 0

Wondering if anyone else has seen this ?

@wbashir
Copy link
Author

wbashir commented Oct 24, 2013

@onmodulus any word on this, i removed demeteorizer and I still get this issue.

@InconceivableDuck
Copy link
Contributor

How exactly are you using Demeteorizer? You mention "plugin" and "removing it", which leads me to think you're no quite using it correctly. Demeteorizer is a standalone command line tool, not meant to be included in other projects.

@wbashir
Copy link
Author

wbashir commented Oct 24, 2013

Yes i understand its a CLI and I have been using it since Meteor 0.5.0+ to deploy. I installed/removed it with npm and i am confused myself as to why this error occurs when I am running my application. I have a deploy script (.bash) which isn't managed or read by Meteor and I have started removing meteorite packages to see which ones cause this problem. I have nailed it down to the meteor-handlebars server package and i will see if i can reproduce with a GIT repo to show what i mean

@InconceivableDuck
Copy link
Contributor

Hmm, still not sure what's going on. Can I see the rest of your npm install output?

@wbashir
Copy link
Author

wbashir commented Oct 27, 2013

npm http GET https://registry.npmjs.org/demeteorizer npm http 304 https://registry.npmjs.org/demeteorizer npm http GET https://registry.npmjs.org/commander npm http GET https://registry.npmjs.org/fs-tools npm http GET https://registry.npmjs.org/async npm http 304 https://registry.npmjs.org/commander npm http 304 https://registry.npmjs.org/fs-tools npm http 304 https://registry.npmjs.org/async npm http GET https://registry.npmjs.org/keypress npm http GET https://registry.npmjs.org/lodash npm http 304 https://registry.npmjs.org/keypress npm http 200 https://registry.npmjs.org/lodash /usr/local/share/npm/bin/demeteorizer -> /usr/local/share/npm/lib/node_modules/demeteorizer/bin/demeteorizer demeteorizer@0.3.1 /usr/local/share/npm/lib/node_modules/demeteorizer ├── async@0.2.9 ├── commander@1.1.1 (keypress@0.1.0) └── fs-tools@0.2.10 (lodash@1.0.1)

@InconceivableDuck
Copy link
Contributor

This output is showing everything installed correctly. Where does the error occur?

@wbashir
Copy link
Author

wbashir commented Oct 28, 2013

The error in my first post occurs only when i run my application against the newest meteor release meteor --release 0.6.6.2 This might be a meteor issue but i can't seem to figure out what is looking for demeteorizer and the required by `undefined@undefined`` doesn't really help. I will post this question on meteor-talk and see if anyone else is having similar problems.

@wbashir wbashir closed this as completed Dec 18, 2013
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