Open abinavseelan opened 6 years ago
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 !
ready to use graphql crud with apollo would be realy nice
graphql is a example π
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 ?
When can we expect new version of MERN ?
Maybe add a default landing page.
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!
Would love to have swagger/jsdoc support
@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?
How can I store image using this repo?
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.
My 4 suggestions:
@connect
for Redux.SASS
and SCSS
syntax.xip.io
or browserSync
, which serves the site in the local network so we can test on our mobile devices.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.
I hope in big MERN update, the official web page will use React. π π π
Is this project still active? Haven't seen any commits or PRs merged since a month... Is any other branch being used?
Waiting for this...
I'm also waiting for this and very excited, any updates on progress? @abinavseelan, Thanks!
What about this param for installation? --scripts-version=tsx or jsx
I'm also waiting for this and very excited, any updates on progress? @abinavseelan, Thanks!
Looking forward to trying this out π
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 :)
Yes, at least an update on progress would be amazing :)
How's the work on version 3 going? Will it, also, support JSX files?
It looks dead to me. I'd like to contribute as soon as I graduate
Hello,
I noticed that the maintainer is to longer working at Hashcode since March. Is that supposed to mean that v 3.0 is never going to be release? @abinavseelan please leave your comments.
I think it is a good time to fork the project into another repository, where it can be actively maintained.
On Sat, May 26, 2018, 5:04 PM Andrey Gruniov notifications@github.com wrote:
Hello,
I noticed that the maintainer is to longer working at Hashcode since March. Is that supposed to mean that v 3.0 is never going to be release? @abinavseelan https://github.com/abinavseelan please leave your comments.
β You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/Hashnode/mern-starter/issues/344#issuecomment-392255571, or mute the thread https://github.com/notifications/unsubscribe-auth/ABzb3WYm8svqS_NtITpytMrgof7NdzRjks5t2T3VgaJpZM4RmiWq .
Hey all π
Thank you for your interest in this project. We started the new version ambitiously a few months back, but due to a sudden change in the priorities of the company, we had to delay it.
However, we love MERN, and we want to finish version 3.0. We are currently looking for active maintainers for this project who can help us release the next version asap. If you are interested, please leave a comment below, and we will get back.
PS: Out of love, the Hashnode team would be sending Power MERN Tees and dev stickers to all the new maintainers of the project. β€οΈπΊ
@fazlerocks please add me to the team I'll help out. I also have a deep interest in this version 3 to be completed as we have a pending course on MERN Essentials at Lynda/Linkedin Learning I'd like to record sooner than later.
So add @mannyhenri to the maintainers and I'll take a look at where the version is and see how I can give a hand.
Hi there @fazlerocks! I'm interested in being an active maintainer of MERN. Reach out and let's chat; there's likely some logistics to figure out with bringing community developers like myself onboard (since MERN development has thus far been managed exclusively by Hashnode employees, if I understand correctly). There's a lot of work to do to hit the "MERN 3.0" milestone, and even more potential work beyond that, if we wish to keep MERN modern with respect to our community as a whole. I'd very much love to be a part of it! π»π
I am interested. I am currently in a coding bootcamp at the University of Miami and they are focused on teaching the MERN stack. I don't know how much I can contribute as a "junior" developer but I'd love to help out if possible.
Having just started a MERN project on next.js because this project seemed abandoned, I'm also interested in contributing.
Wow! @fazlerocks with all of us @mattlubner @rosariorussell @jayarnielsen we should be able to bring V3 faster than a parsec! (sorry just saw Han Solo, had to say it). :shipit:
@fazlerocks might it make sense to add a board to the ongoing MERN V3 repo with a todo list as issues
and assign them to each of us. You guys probably have something already going, if not, I'd be glad to do a quick rundown of ongoing items, wishlists (what makes sense for V3 and what should be done for later)...like we always say...ship less but have more updates so the MERN community benefits from ongoing updates until we get to V3. And V3, might be simply bringing all dependencies to latest versions and then we look into the future of what can be added?
Yes, that's a great idea. I will get back with the current status of the project by tomorrow EoD. @mannyhenri
Iβll gladly spend some time on this project if weβre able to go off a roadmap like @mannyhenri suggested ππΌ
I'll be happy to contribute in v3.
@fazlerocks I would love to contribute in V3.
I would also like to help this project :)
I'm also interested in contributing to V3. Let me know once you have a roadmap put together.
@fazlerocks let me know if you need my help in putting the roadmap together. We have lots of people willing to get started, eager to get this going! ;)
@fazlerocks, I would love to help out as well.
Welcome the new maintainers of MERN project. @mannyhenri @mattlubner @rosariorussell @jayarnielsen
Hello, I've been following this thread since last year, and I'd like to contribute to V3 of this project.
On Wed, May 30, 2018, 9:08 PM Syed Fazle Rahman notifications@github.com wrote:
π’Welcome abroad
Welcome the new maintainers of MERN project. @mannyhenri https://github.com/mannyhenri @mattlubner https://github.com/mattlubner @rosariorussell https://github.com/rosariorussell @jayarnielsen https://github.com/jayarnielsen
β You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/Hashnode/mern-starter/issues/344#issuecomment-393300553, or mute the thread https://github.com/notifications/unsubscribe-auth/AVV-VbmTbpvAospFlnrEpc1DckbVI_D-ks5t3vwxgaJpZM4RmiWq .
All let me know anyone that haven't been added to the maintainers and would like to help out. The team is working on a board where we can define a realistic timeline and issues related to it to get to V3!
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:
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