-
-
Notifications
You must be signed in to change notification settings - Fork 29
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
Cannot use aldeed:schema-index
, getting error "index" is not a supported property
#41
Comments
Does this work well without webpack? |
Yes, I think it might have something to do with the fact that
I'll probably have to figure out how the code in |
I just had this issue too. It might be possible that schema-index loads first and the simpl-schema gets loaded and reconfigured somehow and that removes the extended options. Im going to try to add package functionality in app code and check if that works. @nicu-chiciuc where you able to find a solution? |
I was able to workaround the schema-index issue by not importing the schemas in the client code. |
@pmogollons We left the idea of switching to meteor-webpack for awhile since it wasn't crucial at the moment, but I'll definitely try your solution when I'll get around to it. |
Can you share your webpack configuration? |
Unfortunately I was not able to make the project work correctly app compiles without issues but get an error on browser console. I think the problem is related to issue #40 Here goes my webpack config.
|
I'm having this issue with
aldeed:schema-index
although I think the same issue would apply also to other meteor packages. Basically what this package does is add several options to SimpleSchema.The problem is that I'm getting the following error:
I've tried to use your example of React by adding
simple-schema
and I'm getting the exact same error.It seems like the meteor package is not executed or is using a different version of SimpleSchema.
Or maybe I missed something in how to actually use this package since I don't have much experience in meteor.
The text was updated successfully, but these errors were encountered: