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...
Related
I have downloaded angular 2 application from this link:
https://github.com/aravindfz/firstAngular2App
How to run this application?
Which angular cli version install to run angular 2 application?
I tried from some questions stackoverflow but not working properly.guys this question is not duplicate..Please understand.
Anyone can give clear details?
I need step by step procedure.
If you cloned the repo and did nothing else, there are a few things you need to do before you can run the app. Since I don't know how much web development you have done, I'm going to include things some people will think unnecessary.
Install node.js, if you haven't yet. Grab the LTS release from https://nodejs.org/en/. Do not use the "Current" version, because that may not be compatible with Angular just yet. If you have and older version of Node, upgrade. If you already have the LTS version, skip this step.
Now open a new command prompt or terminal and change to the directory where you cloned the repo. To be sure you're in the right place, make sure you can see a file named package.json.
In this command prompt/terminal window, execute this command: npm install. This will download and install all the dependencies (which could rather disturbingly add up to a few hundred Megabytes). You may experience timeout errors if you're behind a corporate proxy server. That's not something you can fix as of 2018. Just connect using something else and try again.
Once everything is installed, you should be able to run the Angular app. Everything I mentioned already only need to be done before you run it the first time. To ensure you are in the right folder, navigate to where your index.html is located and run this command: ng serve. If ng cannot be found, you may need to install it. To do so, execute npm install --save-dev #angular/cli. Now it should work. If not, close your command prompt/terminal window, open a new one and try ng serve again.
Once ng serve is finished compiling, you should be able to view your app by opening http://localhost:4200 in your favourite browser.
And that's it!
Here's a bonus tip: Take the time to work through the official Angular Quick Start. It really is a fantastic guide and will get you skilled up much quicker than just hacking it ever will.
Good luck.
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 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 checked out 86a52e6 on the master branch from the Meteor repo. Ran ./scripts/generate-dev-bundle.sh per the Slow Start (for developers) instructions. This goes off to work for awhile, generating a ton of output but ending with errors. All of them seem to be unused private fields in third-party libraries.
Has anyone seen anything like this? Any guidance would be most welcome! I've been getting to know my way around Meteor via the pre-compiled binaries, but this was my first attempt to build from scratch.
Running OSX 10.8.5.
Thanks in advance!
You don't need to compile your own dev_bundle. On first time you run meteor from the checkout, it will download compiled binaries (mongod, mongo, node and npm) for your system architecture.
Don't bother yourself compiling, just use ready binaries.
I have suddenly started getting the following message - all seems to work but i don't know why im getting it / what it really means for my app.
The only thing i can think of is that some smart-package im using is looking for an older version of meteor, and mrt is clever enough to not use a meteor version that will break it?
Stand back while Meteorite does its thing
Done installing smart packages
Ok, everything's ready. Here comes Meteor!
=> Running Meteor from a checkout -- overrides project version (0.6.2)
The thing is i'm pretty sure i want to be running on 0.6.2 not overriding it to some other version.
So what does this mean really? - and what do i need to do to not get it.
Thanks
I'm not too sure why it uses that odd terminology. Version 0.6.0 introduced project versions, so each project could run its own version of meteor similar to how meteorite does with smart.json
What Running Meteor from a checkout -- overrides project version (0.6.2) means is this version is overridden by the version in your smart.json. Typically the latest version on the master branch on github (which is checked out hence the wording). So at this moment if you ran mrt it would use 0.6.2.1
I'm sure over time meteorite will eventually be folded into meteor. 0.6.0 was just released a short while ago so some updates still need to be done to make them work better together.