Closed optilude closed 9 years ago
I think this may be a red herring. The packages
syntax probably works, but there is an error in the loaded code that breaks the package client-side, and so I think it never properly registers as a module.
Ok I will monitor issue on the react-packages repo. We have some problems with "different Reacts" because of browserify before, but it never makes modules to crash/not load/not register like in your case, I will take a look at this.
Aside double-react issue, with new version there is no more need to define System.config({packages: {...}})
Index module is loaded out of the box, and the old syntax could actually produce Maximum call stack size exceeded
error. See docs for more info.
Please reopen if problems still occur.
Hi,
In
meteor-react-example
(https://github.com/optilude/meteor-react-example), I have this inpackages/app-deps/system-config.js
:That used to allow me to do imports like:
However, upon upgrading to the latest Meteor and
universe:modules
this no longer works. I get the following error:I also tried:
This seems to remove the error from startup of the server, but I'm getting errors client-side because SystemJS seems to be trying to fetch
app-deps
as a file and this returns a skeleton HTML page.What am I doing wrong? Right now, the
meteor-react-example
is not working for people who try to use the latest versions. :(