You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey thanks for a great repo, it's very nice! Only one thing bugs me a bit. The dependencies are duplicated, one has to install same libraries in node_modules and jspm_packages. It's not a huge problem but it would be more elegant to be able to use jspm everywhere, also in testing. Do you have idea how this could be solved?
This thing could also introduce issues, in this case for example I can see that you have a different version of react in node_modules and in jspm_packages .
The text was updated successfully, but these errors were encountered:
yes I do. I have it solved on another project of mine. JSPM is isomorphic, so it runs in node.js as well. So running tests from JSPM dependencies is not a big problem. Will try to update the tests here with JSPM dependencies instead of NPM.
Ok great to hear, looking forward! I'm currently experimenting with JSPM in a react project and so far it's looking pretty good, my only issue (likely unrelated to this one) is that my tests are not able to locate sub-components with module not found errors... anyway, let's just close the issue.
Hey thanks for a great repo, it's very nice! Only one thing bugs me a bit. The dependencies are duplicated, one has to install same libraries in node_modules and jspm_packages. It's not a huge problem but it would be more elegant to be able to use jspm everywhere, also in testing. Do you have idea how this could be solved?
This thing could also introduce issues, in this case for example I can see that you have a different version of react in node_modules and in jspm_packages .
The text was updated successfully, but these errors were encountered: