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.
Related
I'm getting the following error when I try and create a new meteor project:
C:\Users\joshm\AppData\Local\.meteor\packages\meteor-tool\1.4.2_1\mt-os.windows.x86_32\dev_bundle\lib\node_modules\meteor-promise\promise_server.js:190
throw error;
^
SyntaxError: Unexpected token
this is a new problem and as a bit of backstory of how I got to this point:
1) yesterday my project was working perfectly, however I realised that not all of my packages were up to date. It appeared if some had dependancies on others and so couldn't update any further, I removed most of them to see if I could update the specific one I wanted to update
2) now with many of the packages uninstalled I tried to update and I got the same error as I'm getting above. When trying to run the project I also get the same error. I put the packages back in where they were before in hopes that it will fix the problem
3) adding the packages back in doesn't fix the problem and I still get the same error when trying to run the project. I copied all of my document files into a new folder and tried to make a new project to get a clean start
4) when trying to create the new project I get the same error. However it appears as if all of the standard Meteor files are created - the clicking counter. I attempt to run the new clicking counter and once again get the same error, and I also got a firewall alert which I've never had before when trying to run a meteor project.
You can try deleting .meteor from your home directory, and re-install meteor.
for me deleting local meteor installtion on C:\Users\joshm\AppData\Local.meteor\ wasn't enough.
I also had to delete
.meteor/local folder inside my project folder
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.
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'm using
Meteor 1.0.2.1
sanjo:jasmine 0.9.1
velocity:html-reporter 0.3.2
https://doctorllama.wordpress.com/2014/09/22/bullet-proof-internationalised-meteor-applications-with-velocity-unit-testing-integration-testing-and-jasmine/ says I should be able to use console.log() to see output in the console.
But nothing happens for me.
If I move the call out of tests/jasmine into client/ or server/ then the output is on the terminal where meteor is run.
The html-reporter also has a section called Logs. Looking at the code it appears to have a reactive collection on VelocityLogs. My google-fu is failing me as I can find no information on how to get any output to display in this section.
What is the correct way of logging in jasmine tests?
In Chrome the client side logs are visible through the JavaScript Console.
But I still don't know where the server side logs might be.
I've run with DEBUG=1 JASMINE_DEBUG=1 VELOCITY_DEBUG=1 VELOCITY_DEBUG_MIRROR=1 and the console logs do not appear either.
Edit:
I've created a repo to provide an example of the problems at https://github.com/baerrach/meteor-velocity-issue-223.
If you are running server integration tests and they're not appearing, you may have found a bug!
Try running with:
VELOCITY_DEBUG=1 meteor
The logs should appear in the same place as the main meteor logs appear, prefixed with [velocity-mirror]
I am working on a Windows machine with Meteor 0.8.1, and I am trying to get the cloudinary package (from git user Lepozepo) to work. I reverted the package to a version prior to the Meteor 0.9 changes to package handling, so it should be compatible with the version of Meteor that I am using. I followed the readme, and things appear to work on the client side. But when it tries to call the server method - I've tried both 'cloudinary_upload' and 'cloudinary_upload_stream' - the server throws an error: Exception while invoking method 'cloudinary_upload' undefined
The method is clearly defined in the server.js file. I've verified that the package is installed. I have no idea why meteor can't seem to find this method, and worse, I have no idea how to troubleshoot it.