What if your project can have a startup.js file that would be loaded in Meteor without Webpack. Would it solve your problem?
Nope. Still doesnât update the page =(
You might want to try the last version I just released. Iâve tried it on Windows and the hot-reload seems to work. However, it is significantly slower than with Mac or Linux. And it does seem to only work 90% of the time. Thatâs weird
Do I need to install anything? Itâs still not working for me. The console says âClient modified - refreshingâ but the client stays the same =/
That should fix it⌠basically if you could symlink or copy that startup.js file into the âmeteorâ folder, that would startup at the normal time. Putting it in a lib folder would prob. be best.
Awrrr, Iâll try new things. It should work. CLI webpack watch is working fine with Windows .
The compiler will take care of it. No need to copy anything, itâs the beaty of plugging it directly with Meteor isobuild.
What if every startup.js files were processed by Meteor like a regular JavaScript file. Would it be problematic? The term feels generic to me.
I know how frustrating it is for you =/
Thanks
Due to popular demand by @SkinnyGeek1010 @mquandalle @garrilla @none
Here is the kickstart-flowrouter project
Thanks to @arunoda for the FlowRouter. I would love your opinion on this!
Maybe a dumb question:
Would it work with Blaze (without react) ?
Sure, I donât see why it shouldnât work. You can remove the ReactRouterSSR, react⌠packages and just enjoy module import/exports.
But you wonât get improved reload times and most of the blaze extensions/libraries are available through the Meteor package system - These packages still exposes globals but can be used with âfake packagesâ (externals in webpack config)
Yes it is possible. I think someone wrote something to use webpack hot module replacement with Blaze. Here is an example of Webpack with Blaze. You probably could adapt it to webpack:webpack.
MAJOR UPDATE
Iâve made a major fix for building in production. It was taking forever and I couldnât figure out why. Turns out private/webpack.stats.json was responsible for that. It was triggering a new build over and over. You can now access the global variable WebpackStats instead of reading the private file webpack.conf.js.
If you tried it in production mode before, you will see a huge improvement
Coool! I have to try this! (-:
Is it correct to say that modules
is the equivalent of Meteor packages? So, for example, instead of adding a thereactivestack:todoapp
you develop a module under ./modules
: https://github.com/thereactivestack/kickstart-hugeapp/tree/master/modules/TodoApp.
And then the equivalent of doing meteor add thereactivestack:todoapp
is doing import TodoApp from './TodoApp'
, right?
Also wondering how could it handle requires per module? For example, a certain module might require a Meteor or npm package, but avoid including the module dependencies, unless the module is imported somewhere in the app.
How do you debug server side code?
I tried:
- meteor debug / node-inspector
- WebStorm debugging
However, nothing works. Probably, I am donig something wrong. Could you tell me if server side debugging works for you? If so, could describe shortly steps that you take?
Thanks
if I add a react atmosphere package e.g. izzilab:material-ui
How do I import the react components?
I havenât tried node-inspector yet but I suppose it is possible. It is on my todo list but I canât help at the moment.
Exactly the same way you would with a regular Meteor project. YOu have access to global variables the package create. You can do like in their example:
const {
AppCanvas,
AppBar,
Styles,
RaisedButton,
DatePicker
} = MUI;