Did you see my post yesterday?
You MAY have the same issue. If you look at the source (maybe put some console.logs) it may answer the question of why you are having so much grief.
Did you see my post yesterday?
You MAY have the same issue. If you look at the source (maybe put some console.logs) it may answer the question of why you are having so much grief.
Use the workaround and wait for MDG to investigate all issues created by migration to 1.3
As long as your code works, IMHO, your are good until we get more information.
just saying that I stumbled upon something similar with incuding select2
AFTER migration to 1.3.
For me the only working solution right now is to load the library via CDN in - adding it via npm
does NOT work for me.
this is the select2-problem on github https://github.com/aldeed/meteor-autoform-select2/issues/65
Thanks for all your answers. It’s likely that my jQuery plugins have the same problem as those pointed out by @stocksp. For the moment I’ll go with the workaround and hope for a better Meteor 1.3.2.
I opened a GitHub issue for CLNDR as well: https://github.com/kylestetz/CLNDR/issues/257
I actually was able to remove the momentjs:moment
from .meteor/packages
and just use the one installed by meteor npm install --save moment
I added a file npm_modules.js in /lib
containing
moment = require('moment')
All 3rd part libraries find the global variable