Closed jasonschock closed 6 years ago
It seems as though switching Match.Where
to method shorthand syntax in this commit caused it to no longer be usable as a constructor. Instead, Match.Where
should now be called as a function, without new
. Invoking it as a constructor was creating an unnecessary object before, so this change would be a good idea even if it wasn't strictly necessary.
Seeing the same problem with aldeed:simple-schema@1.5.3 running METEOR@1.6.1-beta.18
=> Exited with code: 1
W20171213-11:42:54.253(-8)? (STDERR) /Users/jim/.meteor/packages/meteor-tool/.1.6.1-beta.18.1cdl7le++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/server-lib/node_modules/fibers/future.js:280
W20171213-11:42:54.253(-8)? (STDERR) throw(ex);
W20171213-11:42:54.253(-8)? (STDERR) ^
W20171213-11:42:54.254(-8)? (STDERR)
W20171213-11:42:54.254(-8)? (STDERR) TypeError: Match.Where is not a constructor
W20171213-11:42:54.254(-8)? (STDERR) at packages/aldeed_simple-schema.js:1547:26
W20171213-11:42:54.255(-8)? (STDERR) at packages/aldeed_simple-schema.js:2160:4
W20171213-11:42:54.255(-8)? (STDERR) at packages/aldeed_simple-schema.js:3128:3
.
.
.
@aldeed Any chance PR #723 gets merged and a new version (1.5.4) published to Atmosphere or should we just fork? There are a number of reasons why we can not upgrade to the NPM package version of simple-schema. And if there was any way to merge in PR #616 that would be even more awesome as this fixes another issue for us and many other users. Thanks!
upgrade to 1.6.1 beta too, same issue here.
If you don't want to create your own fork you can install ours as a local package. https://github.com/clozertech/meteor-simple-schema We also merged #616. Works great with Meteor 1.6.1.
The Meteor SimpleSchema package is no longer maintained other than critical fixes to keep it running with each latest Meteor release. Closing non-critical issues in this repo. Anyone who cares about this may do one or more of the following:
Please see issue meteor/meteor#9383 for context and specific https://github.com/meteor/meteor/issues/9383#issuecomment-345675174.
Basically, this error is now appearing with Meteor 1.6.1 beta on boot:
Per comments by @abernix: