-
Notifications
You must be signed in to change notification settings - Fork 19
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
config.meta.deps is not an array in the browser (breaking systemjs) #44
Comments
systemjs/systemjs#769 (comment) |
I'm not 100% sure who's at fault here. I would say it's Karma for not passing arrays from the framework (nodejs) to the browser with the proper Array prototype - I would have thought it was using JSON methods to pass the I could change the framework to encode the SystemJS config as a JSON string, then decode it in the adapter. That should solve the problem for you. |
I have created bugs on |
Hey @unional |
I guess this is a bug in
karma
and notkarma-systemjs
but I want to bring it up here as I discover and start the conversation fromsystemjs
.A apologize that this is quite long because it was very difficult to trace, so I want to give you as much information as possible.
The resulting bug of this issue is
systemjs
will fail with the following error:After tracing the rabbit for a long time, the problem lies in
meta[module].deps
is not an array after it is loaded inkarma
.As the basis of my example, I have the following in my config:
In
karma-sysmtejs
adaptor.run
:produces:
However, I validate that in
index.js
, at the end of initSystemjs:produces:
Because the
instanceof Array
failed, it fail the following code insystemjs
.In
proto.js
:This cause the
deps
becomes anobject
instead of an array, thus missing theconcat
method and failedsystemjs
.Do you think this is purely
karma
bug?The text was updated successfully, but these errors were encountered: