Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not compatible with Meteor 1.7 #137

Open
mishantidev opened this issue Jun 27, 2018 · 5 comments
Open

Not compatible with Meteor 1.7 #137

mishantidev opened this issue Jun 27, 2018 · 5 comments

Comments

@mishantidev
Copy link

mishantidev commented Jun 27, 2018

Getting this error on Meteor 1.7.0.3. Downgrading to Meteor 1.6.1.3 solves the problem.

Template.languageSelector.onRendered(function() {
	this.$('.ui.dropdown').dropdown({on: 'hover'})
})

TypeError: this.$(...).dropdown is not a function
at Blaze.TemplateInstance. (forms.js:12)
at blaze.js?hash=a1ff2d6d5ecd59ee11e2ba260b8650a9d1140f59:3398
at Function.Template._withTemplateInstanceFunc (blaze.js?hash=a1ff2d6d5ecd59ee11e2ba260b8650a9d1140f59:3744)
at fireCallbacks (blaze.js?hash=a1ff2d6d5ecd59ee11e2ba260b8650a9d1140f59:3394)
at Blaze.View. (blaze.js?hash=a1ff2d6d5ecd59ee11e2ba260b8650a9d1140f59:3487)
at blaze.js?hash=a1ff2d6d5ecd59ee11e2ba260b8650a9d1140f59:1845
at Object.Blaze._withCurrentView (blaze.js?hash=a1ff2d6d5ecd59ee11e2ba260b8650a9d1140f59:2271)
at blaze.js?hash=a1ff2d6d5ecd59ee11e2ba260b8650a9d1140f59:1844
at Object.Tracker._runFlush (tracker.js:511)
at onGlobalMessage (meteor.js?hash=c8108d734cc548d91539b054e14b613d0c4512cc:466)

@mishantidev mishantidev changed the title template.$(...).dropdown is not a function Not compatible with Meteor 1.7 Jun 27, 2018
@tvogt
Copy link

tvogt commented Jul 11, 2018

confirmed for radio checkboxes as well:

Template.CreateForm.onRendered(()=>{
this.$('.ui.radio.checkbox').checkbox();
});

Exception from Tracker afterFlush function: meteor.js:1010:11
TypeError: this.$(...).checkbox is not a function meteor.js:1010:11

@rdsimp
Copy link

rdsimp commented Jul 18, 2018

I fixed this by including the following for dropdown:

import '../../client/lib/semantic-ui/definitions/modules/dropdown';
import '../../client/lib/semantic-ui/definitions/modules/transition';

@vbelolapotkov
Copy link

@anjunatic are you still using eager file loading outside of imports folder or switched to package.json entry point options?

@mishantidev
Copy link
Author

@vbelolapotkov I use ES6 modules & imports folder for my own files, but semantic UI is located in client folder

@vbelolapotkov
Copy link

@anjunatic if you start a meteor 1.7 project from scratch it will create meteor section in you package.json which disables default loading order from your client folder => you have to import your client folder manually. If you want to stick with the old loading behavior just remove meteor section from your package.json and it will load semantic ui.

Anyways, as this package is falling behind the original npm package updates I switched from atmosphere package to npm in the following way:

  1. build js, css, assets from npm package with gulp (in a separate directory)
  2. add compiled files via local package

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants