The main advantage for developers using the MERN stack is that every line of code is written in JavaScript. This is a programming language that’s used everywhere, both for client-side code and server-side code. With one language across tiers, there’s no need for context switching. For tech stack with multiple programming languages, developers have to figure out how to interface them together. With the JavaScript stack, developers only need to be proficient in JavaScript and JSON. Overall, using the MERN stack enables developers to build highly efficient web applications.
Mernless provides a powerful Boilerplate which makes it easy to build isomorphic apps using Mongo, Express, React and NodeJS. It minimises the setup time and gets you up to speed using proven technologies. Mernless takes the pain out of development by easing common tasks used in many web projects, such as:
- Scalable and Maintainable Mern architecture
- Robust routing
- Database caching
- JWT authentication
- (Redux, Mail, Swagger, Docker, Travis) integration
- Command-line interface
Before you install Mernless, you should check to make sure that your system has the proper prerequisites installed. These include
- Node.js >= 8.0.0
- npm >= 6.10.3
- Clone the repo and cd into it
- Rename or copy .env.example file to .env
- Run node geek generate:key .env
- Set your database credentials in your .env file
- Run npm install
- Run npm run serve
- Run npm run start
- Visit localhost:8000 in your browser
If you discover a security vulnerability within Mernless, please send an e-mail to Yasser Ameur El Idrissi via getspookydev@gmail.com . All security vulnerabilities will be promptly addressed.
If you've found a problem in Mernless which is not a security risk, do a search on GitHub under Issues in case it has already been reported. If you are unable to find any open GitHub issues addressing the problem you found, your next step will be to open a new one. (See the next section for reporting security issues.) your issue should contain a title and a clear description of the issue. You should also include as much relevant information as possible and a code sample that demonstrates the issue. The goal of a bug report is to make it easy for yourself - and others - to replicate the bug and develop a fix. Remember, bug reports are created in the hope that others with the same problem will be able to collaborate with you on solving it. Do not expect that the bug report will automatically see any activity or that others will jump to fix it. Creating a bug report serves to help yourself and others start on the path of fixing the problem.
- Contribute to the core repository.
- Ask your employer to use Mernless in projects.
- Make a tutorial that you explain Mernless.
- Follow our Mernless repository.
The Mernless Boilerplate is open-source software licensed under the MIT license.