Using npm on Meteor 1.3 + angular1 (bump!)

help
1

Anyone updated an angular1-meteor project to 1.3 and is succesfully using npm?

I’m bumping against issues, posted on http://stackoverflow.com/questions/36507467/how-to-migrate-an-angular-meteor-project-from-metoer-1-2-to-1-3-and-start-using

Specifically, I’m bumping against:

“Can’t find npm module ‘ecmascript’. Did you forget to call ‘Npm.depends’”

Cheers!

2

I eventually got my 1.2 Angular1 app mostly working from 1.3. Unfortunately it was a lot of hacking the thing to death before I got it to work so I don’t have a proper methodology to give you.

One thing I would note though, I would remove angular-meteor package, instead I would use angular-templates with ecmascript as per their new sample.

My package.json looks has this (took out the ones specific for my app and stuck to what most people would have) …

"dependencies": {
    "angular": "^1.5.3",
    "angular-animate": "^1.5.3",
    "angular-meteor": "^1.3.9",
    "angular-meteor-auth": "^1.0.1",
    "angular-sanitize": "^1.5.3",
    "angular-ui-router": "^0.2.18",
    "meteor-node-stubs": "~0.2.0"
  }

I say mostly earlier because I am still having some issues with FindFromPublication losing the data when I have multiple subscriptions against a collection and not all of them are using FindFromPublication. I still have a few headaches with Meteor.users with it. At the moment trying to build a small test app so I can prove the issue with https://github.com/versolearning/find-from-publication/issues/7 (but there’s no such thing as small angular-app yet) so I’m building again from semi-scratch using the angular-meteor example