I accidentally created a collection accounts ... yes I know I wasn't thinking;
it was really dumb of me. But now my Meteor installation is broken completely.
for code like Accounts.createUser server hangs and returns error 'method createUser undefined.'
OS is windows10
I have tried uninstalling and re-installing Meteor, removed and re-added accounts-.. nothing works. and of course the collection is no long 'accounts'
Please help if you might have an idea how to resolve this..
Remove all your accounts collection code (assume you have done that already)
Stop your server
Run meteor reset (from the command line in your project directory where you run meteor)
Restart your server
That should do it.
Related
I've installed the latest version of meteor 1.4.2.3 and simply trying to create my first meteor app. The steps are simple but the process keeps looping on "Starting your app".
I've searched for solutions and tried the following with no success: meteor update, changing the port, npm install, meteor reset, uninstall and reinstall.
Stuck at "Starting you app" seems to be a common issue with no consensus on solution.
Please someone help!
Meteor needs quite a bit of memory, if you have less than 8GB it will struggle.
Sometimes just control-c it and starting it again works.
Sometimes it needs a
meteor reset
Another thing you can do is remove
<project-dir>/.meteor/local
Usually the problem only rears its head once in a while
I met this issue too. And Meteor stuck suddenly, it was working fine a day before. I tried everything. Uninstalling,reseting meteor, updating meteor, updating npm, meteor npm cache clean,Registry editing etc. Nothing helped. Then,
I updated my Windows 8.1 to Windows 10 and it was working again.
Edit: try this method first.
https://stackoverflow.com/a/46133529/3959840
I just downloaded meteor for Windows V 1.5.2. In my case I did not have Mongo DB installed.
I downloaded it from here and in cmd I set the MONGO_URL=' ' and boom it started my app.
Hope this helps someone :).
I have momentjs:moment added in my list of packages, I checked with meteor list, but whenever I launch meteor shell I'm unable to call moment(), it tells me moment is 'undefined'.
It seems as though my app is able to execute code containing calls to moment(), shouldn't I also be able to do the same from meteor shell?
I fixed the problem I was having by updating my version of meteor to 1.1.0.1. I don't know what was causing the error previously, but updating took care of the problem.
I am learning meteor to build an app. I am finding things pretty unstable with Meteor. I am using Ubuntu 14.04 and Meteor 1.0.3
Everything is working fine and I had finished couple of Modules. And Suddenly one day, I get this error:
Can't find npm module 'mailcomposer'. Did you forget to call 'Npm.depends' in package.js within the 'email' package?
I know that 'mailcomposer' package is not there and installed it and worked well.
And again, projects work fine and again one day suddenly I get this error:
Cannot find module 'fibers'.
I really want to know what is happening. I have not removed any module nor did I add one. My project was running fine, but later when I opened the system I got the error. Does meteor remove or update modules automatically in the backend? Rather than fixing these errors, I want to know why modules are suddenly being removed.
I am novice in Meteor, apologies if the question is stupid.
I had this issue when I was deploying an Meteor app on Digital Ocean, for some reason I had to reinstall nodejs and fibers package to make it work again.
Are you switching from 1 node version to another?
If you are on the server:
get meteor's node version meteor node -v
verify if the server is using the same node version by node -v
Let me know...
I am having trouble with my Meteor up, which is perfectly functional on localhost and on Modulus. When I try to deploy to a *.meteor.com instance the upload fails and I get a very cryptic error. The first line is the gist of it I guess
Error: not a tracked temp dir: /Users/valentin/.meteor/packages/velocity_core/.0.4.5.1dbi101++os.osx.x86_64+web.browser+web.cordova
I have tried installing and reinstalling velocity and tried deploying it with/without, the error persists. There are a bunch of hidden files in the folder the error points too. Deleting the one mention in the error simply creates new ones and throws an error again (naming a different folder though) Does anyone have an idea what it is about?
I had the same problem with another meteor package. It was solved after I delete everything from myapp/.meteor/local/ directory.
I think you can leave your local db there (myapp/.meteor/local/db), but I did not check if it still be working. (I've deleted all and probably it is the same as running meteor reset for your local project.)
OK, this seems to work: You have to manually downgrade the meteor version to 1.0.2.1, by editing .meteor/release and changing the version number. (There's a fix in dev, so it should be solved in a more complete fashion soon.)
Were you trying to deploy while your meteor app still ran in localhost? I faced the same problem for another package but resolved it by stopping my local meteor app first then deploy.
I have created my first meteor app today and am kind of stuck. Everything works extremely well on localhost:3000, very responsive etc. It is a simple task app, where users can post tasks to a feed that displays all tasks an then claim those tasks, removing them from the general feed and putting them into their personal feed. But when I deploy it to a meteor.com server, everything breaks.
This is the js file
https://github.com/valentin-zambelli/brokenjs/blob/master/mvp.js
Accounts.ui.config({
passwordSignupFields: "USERNAME_ONLY"
});
gets ignored and whenever I try to post a new task the page reloads, getting stuck on app.meteor.com/?text=some+new+task and doesnt display the task in the general taskfeed.
I have removed the insecure and autopublish package. Is there anything I am missing here? It kind of seems as if it uses an older, broken build. I also get the ReferenceError: Can't find variable: require when deploying, but I can't really figure out where this is coming from.
I hope someone can help me.
Ok, it was an insanely stupid mistake on my part: The mongodb was still in an older state and caused a conflict. If you have problems deploying your meteor app try
meteor deploy myapp.meteor.com -- delete
This will delete all resources on the server, including the database. Then do a simple
meteor deploy myapp.meteor.com