-
-
Notifications
You must be signed in to change notification settings - Fork 27
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
Wierd Issue #28
Comments
In order to fix the issue I had to add the package as in import on my package. Its odd that this happens only in production, but maybe the docs should be updated to notify users. |
Reopened so my previous comment could be considered |
Seems odd that it was working locally, are you able to reproduce it on an isolated app? |
@dburles turns out its an issue with collection extensions |
This package has been recently updated, have you updated it? Is there any other information you have that may help me see something on my end? |
In production mode this package isnt picking up all of my collections. Most of my collection live in a package lib, because we use the same collections for multiple apps. Any collections imported from a package are not available via.get() or getAll(). If you just run your app locally with --production you can replicate this issue.
The text was updated successfully, but these errors were encountered: