MERN v3.0.0 🚀

[abinavseelan]

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:

• Out of the box Yarn support
• Bring base Node version to v8.x LTS, for all that async-await goodness 😋
• Upgrade to Webpack 3 and move to babel-preset-env
• Migrating to React 16.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

[mattlubner]

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! 😀

[abinavseelan]

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! 🙂

[alexandru-tomescu]

Hi. You could add also a graphql implemententions, /gql/endpoints, this would be great !

[chrisLovesCode]

ready to use graphql crud with apollo would be realy nice

[carloscuatin]

graphql is a example 🎉

[lordknight1904]

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.

[abinavseelan]

@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. 😄

[carloscuatin]

@abinavseelan option flag with the mern-cli 👍

how can we help in the new version of mern ?

[kamalkrishna3000]

When can we expect new version of MERN ?

[lordknight1904]

Maybe add a default landing page.

[lucaskuan]

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.

[abinavseelan]

@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!

[v29neil]

Would love to have swagger/jsdoc support

[lucaskuan]

@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?

[TeodorKolev]

How can I store image using this repo?

[TeodorKolev]

pm ERR! Failed at the mern-starter@3.0.0 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.

[antoniobrandao]

My 4 suggestions:

• Ability to use decorators, eg. @connect for Redux.
• Make the style loader compatible with both SASS and SCSS syntax.
• Include something in the development config like xip.io or browserSync, which serves the site in the local network so we can test on our mobile devices.
• ESLinter config based on Javascript Standard Style.

[mannyhenri]

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.

[antoniobrandao]

Webpack 4 is out. Build performance is so much faster it's worth a look.

[MiloshN]

I hope in big MERN update, the official web page will use React. 💃 😄 😅

[ajile-in]

Is this project still active? Haven't seen any commits or PRs merged since a month... Is any other branch being used?

[mm420admin]

Waiting for this...

[mannyhenri]

@ashifa454 if you're trying to add react-router 4 right away, it might be better to postpone updating react-router as it will introduce many changes to the repo and might be a lot for a one man job. The plan is to get React 16.x and proptypes fix for 2.5, and leave React-router for V2.8. However, I'm not going to stop anyone if they're willing to tackle it all at once, but could be a pretty big task considering...just my 2 cents. Always best to tackle small pieces at a time ;)

For the introduction, @fazlerocks owns both the repo and slack channel and should get you in when he's got a chance.

[ashifa454]

@mannyhenri I have two confusions if you could help me with, so I migrated react 16 and propTypes, but it seems like react- router will need the earlier react, which include the PropTypes.

[mannyhenri]

@ashifa454 ok and thanks for your work on it. I'll take a look at your PR tomorrow, and provide feedback. Most likely we'll end up merging to a separate branch and continue working on it.

[ashifa454]

@mannyhenri thankyou.

[ashifa454]

@mannyhenriI am getting an error while test, and it's possibly because of enzyme V3.x Migration

enzymejs/enzyme#1106

[mannyhenri]

@ashifa454 have you had a chance to work further with the integration of React 16/proptypes?

[mannyhenri]

@alexandru-tomescu @cosmicbuffalo @jayarnielsen @AndrewBestbier @rosariorussell any of you have some cycles to work on integrating React 16/proptypes? FYI most of the work will constitute in updating routes and most likely might end up updating also React-router to V4. Let me know.

[mannyhenri]

@alexandru-tomescu feel free to do a PR if you've worked on it! ;)

[ashifa454]

@mannyhenri sorry I had some college exams but I am continuing it from today, also I have some silly doubts to clear, so will this discussion panel would be a place or should I mail you?

[mannyhenri]

@ashifa454 you can either use this or create a new issue where we can discuss further.

[ashifa454]

I installed React 16.4.0 , Proptype (as separate NPM dependency https://www.npmjs.com/package/prop-types) and Changed Files accordingly
Now while Starting project I am getting an error

• React-Router ( because i think react-router 2.x.x is dependent on PropType by react and because we have updated it to 16 and prop type is not part of it, so its throwing error)

• While Testing it with npm run test it's throwing an error, and probably issue TypeError: Cannot read property 'getPublicInstance' of undefined with react 16 enzymejs/enzyme#1106 .

if those both problems and its explanation in place, so think we need to update react-router alongside with migrating it to react-16, otherwise guide me from here to the right path.

[mannyhenri]

@ashifa454 you are right, we'll need to update React-router so let's head towards doing this. If you have cycles to work on this go for it, @mattlubner will help out this weekend. Also, feel free to take a look at #348 for references.

[ashifa454]

I am on it @mannyhenri, I have some ways to integrate it, let me give it a try and surely I will be needing help @mattlubner.

[mattlubner]

@ashifa454 I'd suggest starting with upgrade/mern-v2.5.0 and updating to react-router v4 first, get that working, commit, and then tackle react v16.

[AlnoorKhan]

@fazlerocks I would like to contribute for this project.
Please add me.

[qiepeipei]

@abinavseelan I would like to contribute for this project.

[mannyhenri]

All, we won't be adding new contributors for the time being, but feel free to create PRs and we'll add your names to the participating folks when we announce the new versions.

[pedrofurtado]

I'm looking forward to this new release! 👍

[mannyhenri]

Of all the names below, who can help drive MERN 3.0 home? We'd like to be able to release this before the new year!!!

@pedrofurtado @qiepeipei @mattlubner @AlnoorKhan @ashifa454 @alexandru-tomescu @cosmicbuffalo @jayarnielsen @AndrewBestbier @rosariorussell , please let me know if you can help.

[ashifa454]

I am on it.

…

On Sun, Oct 14, 2018 at 3:55 PM Manny Henri ***@***.***> wrote: Of all the names below, who can help drive MERN 3.0 home? We'd like to be able to release this before the new year!!! @pedrofurtado <https://github.com/pedrofurtado> @qiepeipei <https://github.com/qiepeipei> @mattlubner <https://github.com/mattlubner> @AlnoorKhan <https://github.com/AlnoorKhan> @ashifa454 <https://github.com/ashifa454> @alexandru-tomescu <https://github.com/alexandru-tomescu> @cosmicbuffalo <https://github.com/cosmicbuffalo> @jayarnielsen <https://github.com/jayarnielsen> @AndrewBestbier <https://github.com/AndrewBestbier> @rosariorussell <https://github.com/rosariorussell> , please let me know if you can help. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#344 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AM_eU8agZlzgRL1DlVu-Bzdnq-ap1vt2ks5ukxEngaJpZM4RmiWq> .

[mannyhenri]

@ashifa454 ok thanks buddy! Can you share the specifics of where you're at? Version you're working from and what you're working on?

[ashifa454]

I am on 2.5 right now and will start initigrating react router 4.x.

…

On Sun, Oct 14, 2018 at 4:02 PM Manny Henri ***@***.***> wrote: @ashifa454 <https://github.com/ashifa454> ok thanks buddy! Can you share the specifics of where you're at? Version you're working from and what you're working on? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#344 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AM_eUwQqQOBLNQ6TquE9dfY1BpQWF1TNks5ukxK1gaJpZM4RmiWq> .

[mannyhenri]

@ashifa254 awesome! Let me know if you have any questions or encountering issues.

[mattlubner]

@mannyhenri I'd be happy to contribute code and PR's!

[mannyhenri]

@ashifa454 we'll let you lead the 2.6 upgrade and if you need help or get stuck with React router 4 ping me or @mattlubner Also just to keep the conversation focused let's create a new discussion/issue for this upgrade instead of continuing on this thread.

[aaronfranke]

How's the progress on this? Is there an ETA? 2018 is almost over.

I'm wondering whether it's better to use MERN 2 or MERN 3 for my project.

[forresthopkinsa]

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.

We'd like to be able to release this before the new year!!!

Welp it's 2019 and it doesn't look like this is going anywhere

[russellr922]

@forresthopkinsa @aaronfranke Yeah I've been waiting for this as well. Might I suggest @feathersjs/cli and create-react-app as two alternatives.