How can we reproduce this bug?
meteor create --release 1.2.1 foundation-testcd foundation-testmeteor add zurb:foundation-sitesmeteorWhat did you expect to happen?
The application to start.
What happened instead?
=> Started proxy.
=> Meteor 1.3.2.4 is available. Update this project with 'meteor update'.
=> Started MongoDB.
packages/zurb_foundation-sites/test/javascript/lib/mocha.css: warn: @charset rules in this file will be ignored as UTF-8 is the only encoding supported
=> Errors prevented startup:
While processing files with ecmascript (for target web.browser):
vendor/jquery/src/intro.js:45: vendor/jquery/src/intro.js: Unexpected token (45:0)
vendor/jquery/src/outro.js:2: vendor/jquery/src/outro.js: Unexpected token (2:0)
While processing files with fourseven:scss (for target web.browser):
/packages/zurb_foundation-sites/docs/assets/scss/docs.scss: Scss compiler error: File to import:
{zurb:foundation-sites}/docs/assets/scss/settings/settings not found in file:
/foundation-test/{zurb:foundation-sites}/docs/assets/scss/docs.scss
While computing assigned variables:
/packages/zurb_foundation-sites/vendor/jquery/src/intro.js: Unexpected token (47:1)
/packages/zurb_foundation-sites/vendor/jquery/src/outro.js: Unexpected token (2:1)
=> Your application has errors. Waiting for file change.
This does not happen if I try it with meteor 1.3.2.4.
I have the same problem, except for me it's only:
While computing assigned variables:
/packages/zurb_foundation-sites/vendor/jquery/src/intro.js: Unexpected token (45:0)
/packages/zurb_foundation-sites/vendor/jquery/src/outro.js: Unexpected token (2:0)`
I had to downgrade Meteor to 1.3.2.4 to make it work.
+1
Same as @nowinskp
Same as @nowinskp on 1.3.3.1
Could this have something to do with it?
jquery downgraded from 1.11.9 to 1.11.8
+1
+1
I downgraded meteor to 1.3.2.4 to get around this issue. jQuery 1.11.9 seems to be the issue and a few of the packages in meteor rely on it in version 1.3.3.1. Using foundation package version 6.2.3.
It seems this is only an issue with meteor and jQuery so we have no control over this.
Also there might be new meteor versions which do not have this issue.
Does does still occur with Meteor 1.6.1?
@ncoden can I assign this to you as you will address some Meteor related stuff?
Bump =)
Yes =) At least for a simple check that v6.5.0 will work correctly on Meteor.
We've released v6.5 for Meteor. If the issue still exists there, please let us know.
Most helpful comment
I have the same problem, except for me it's only:
I had to downgrade Meteor to 1.3.2.4 to make it work.