Match.Where being instantiated as a class, causes error on Meteor 1.6.1 boot
See original GitHub issuePlease 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:
W20171128-13:29:39.919(-8)? (STDERR) /Users/jschock/.meteor/packages/meteor-tool/.1.6.1-beta.11.js08xa.q30b++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/server-lib/node_modules/fibers/future.js:280
W20171128-13:29:39.920(-8)? (STDERR) throw(ex);
W20171128-13:29:39.921(-8)? (STDERR) ^
W20171128-13:29:39.921(-8)? (STDERR)
W20171128-13:29:39.921(-8)? (STDERR) TypeError: Match.Where is not a constructor
W20171128-13:29:39.922(-8)? (STDERR) at packages/aldeed_simple-schema.js:1547:26
W20171128-13:29:39.922(-8)? (STDERR) at packages/aldeed_simple-schema.js:2160:4
W20171128-13:29:39.922(-8)? (STDERR) at packages/aldeed_simple-schema.js:3128:3
W20171128-13:29:39.922(-8)? (STDERR) at infos.forEach.info (/Users/jschock/Code/calliope/calliope/.meteor/local/build/programs/server/boot.js:415:13)
W20171128-13:29:39.923(-8)? (STDERR) at Array.forEach (<anonymous>)
W20171128-13:29:39.924(-8)? (STDERR) at /Users/jschock/Code/calliope/calliope/.meteor/local/build/programs/server/boot.js:414:9
W20171128-13:29:39.924(-8)? (STDERR) at /Users/jschock/Code/calliope/calliope/.meteor/local/build/programs/server/boot.js:468:5
W20171128-13:29:39.924(-8)? (STDERR) at Function.run (/Users/jschock/Code/calliope/calliope/.meteor/local/build/programs/server/profile.js:510:12)
W20171128-13:29:39.924(-8)? (STDERR) at /Users/jschock/Code/calliope/calliope/.meteor/local/build/programs/server/boot.js:467:11
Per comments by @abernix:
It seems aldeed:simple-schema could accomplish the same thing by not instantiating a new Match.Where as if it were a class.
Issue Analytics
- State:
- Created 6 years ago
- Comments:5
Top Results From Across the Web
Match.Where being instantiated as a class, causes error on Meteor ...
Basically, this error is now appearing with Meteor 1.6.1 beta on boot: ... Where being instantiated as a class, causes error on Meteor...
Read more >Meteor Blog - Medium - RSSing.com
Today we're thrilled to announce the final release of Meteor 1.6, which brings the latest stable version of Node.js, an amazing new debugging...
Read more >Untitled
F450 for sale bc, Archeage game of thrones music sheet, Cis 1 ethyl 4 propylcyclohexane, Sta kon crimper erg 2001, Counter missionary judaism,...
Read more >Untitled
Converse ct lady outsider hi black boot, Soft pink roses, Wayne pa best ... Part time course rp, Voglio andare al mare testo,...
Read more >dplR: Dendrochronology Program Library in R
x = FALSE the behavior will be like COFECHA where a missing ring in a series produces a negative lag in the plot...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Seeing the same problem with aldeed:simple-schema@1.5.3 running METEOR@1.6.1-beta.18
@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!
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: