-
Notifications
You must be signed in to change notification settings - Fork 59
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
Comments
@onmodulus any word on this, i removed demeteorizer and I still get this issue. |
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. |
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 |
Hmm, still not sure what's going on. Can I see the rest of your npm install output? |
|
This output is showing everything installed correctly. Where does the error occur? |
The error in my first post occurs only when i run my application against the newest meteor release |
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.
Wondering if anyone else has seen this ?
The text was updated successfully, but these errors were encountered: