mern-starter
mern-starter copied to clipboard
Hashnode
MERN v3.0.0 🚀
Hey 👋
It's been a little over a year since MERN v2 was released. A lot has changed in the React landscape and it's about time we get back to this project to bring it up to speed with 2018. 😄
Progress on this project has been rather slow from our end due us focusing our efforts on development of Hashnode. While retrospecting our open-source contributions, the need for a new version of MERN came to light, as highlighted by the numerous issues and PR’s that have been raised over the past year to update the repository. We apologize for not getting to this sooner.
What's coming 📦
Here is a brief list of the features that we have in the pipeline for the 3.0:
- [x] Out of the box Yarn support
- [x] Bring base Node version to v8.x LTS, for all that async-await goodness 😋
- [x] Upgrade to Webpack 3 and move to babel-preset-env
- [x] Migrating to React 16.x
- [x] Moving from React Router v2 to v4
- [ ] Have a simpler workflow so that you can start your project(s) with much more ease!
Have a request or suggestion? 💭
If you have any feature requests or suggestions, do leave them below and we'll see if we can bring it into 3.0 😄
Update
(27th May, 2018) We're are looking for new maintainers… Read full update
Can we list "decrease start-up time while in development mode" as an official objective? The last point ("Have a simpler workflow so that you can start your project(s) with much more ease!") is a bit vague, and I'm not sure of what that means. It is currently very painful to do server side development in Mern (due to slow restarts), but I would like to see that change!
It would also be lovely to explore using a node require hook to potentially cache-bust JSX on the server side, or really any other way to eliminate the divergence that comes after many code changes, which require server restarts.
I would love to be more involved with and contribute to the Mern community, so please let us know how. Very happy to finally see activity here! 😀
Hey @mattlubner!
The point "Have a simpler workflow so that you can start your project(s) with much more ease!" is more of an umbrella term for things the community needs or might need to help in their development workflow. Once we've aggregated a list of things, we'll update the issue to highlight the specifics that you'd see in v3.0. This includes reducing server startup time, of course! 😄
Thanks for the suggestions! 🙂
Hi. You could add also a graphql implemententions, /gql/endpoints, this would be great !
I am sorry if this might be a little bit out of topic. But why MERN stack build time is much higher than MEAN (in server post-modified rebuild). This is quite time consuming.
@lordknight1904 We're actually looking into this and trying to revamp the build pipeline with v3.0. 🙂
@carloscuatin @chrisLovesCode @alexandru-tomescu
GraphQL sounds pretty exciting! We'll evaluate this and see how we can integrate GraphQL into MERN, without bloating the user experience for users who don't want it.
We have a couple of ideas on how we can manage this, and we're currently floating them around the office to get opinions. 😄
@abinavseelan option flag with the mern-cli 👍
how can we help in the new version of mern ?
Can we start using the 3.0 branch? Cause we have a project that needs to kickstart now and may just use the latest version of MERN.
@lucaskuan
Hey! 👋
I'm sorry. But it's not yet at a stable state to use I'm afraid. 😞 We are doing our best to see this version out as soon as a possible!
@abinavseelan I see, looking forward to have it ready. Will there be a huge migration trouble from 2.0 to 3.0? Any tasks that we could contribute to make it happen faster?
pm ERR! Failed at the [email protected] start script 'NODE_ENV=production ./node_modules/.bin/nodemon server/index.js'. npm ERR! Make sure you have the latest version of node.js and npm installed. npm ERR! If you do, this is most likely a problem with the mern-starter package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! NODE_ENV=production ./node_modules/.bin/nodemon server/index.js npm ERR! You can get information on how to open an issue for this project with: npm ERR! npm bugs mern-starter npm ERR! Or if that isn't available, you can get their info via: npm ERR! npm owner ls mern-starter npm ERR! There is likely additional logging output above.
My 4 suggestions:
- Ability to use decorators, eg.
@connectfor Redux. - Make the style loader compatible with both
SASSandSCSSsyntax. - Include something in the development config like
xip.ioorbrowserSync, which serves the site in the local network so we can test on our mobile devices. - ESLinter config based on
Javascript Standard Style.
All the suggestions above are great but I'd suggest you focus on the main improvements/upgrade such as React V16+, Router V4, Yarn support and webpack latest versions and build other ideas as extensions. This way build times will be shorter and also GTM faster.
Webpack 4 is out. Build performance is so much faster it's worth a look.
Is this project still active? Haven't seen any commits or PRs merged since a month... Is any other branch being used?
I'm also waiting for this and very excited, any updates on progress? @abinavseelan, Thanks!
I'm also waiting for this and very excited, any updates on progress? @abinavseelan, Thanks!
MERN full-stack project as a boilerplate, with all best practices implemented out of the box and latest up-to-date components/modules, including the possibility to easily put-in your own preferable modules sounds so nice! But, looks too good to be true :)
