search

blefnk / relivator-nextjs-template

1,000 stars β†’ 1.3.0 RC β–² Next.js 14 & 15 Websie Template β–² i18n Stripe Shadcn Tailwind Drizzle Zod tRPC TypeScript Clerk Authjs Radix UI, Responsive React 18 19 Server Components, MySQL Postgres Neon TS ORM, Intl App Router Docs User Actions Kit, SaaS Commerce eCommerce Shop Pricing Payments, Dark Mode, Full Stack Free
https://relivator.com
MIT License
981 stars 203 forks source link
drizzle-orm e-commerce ecommerce next-auth nextauthjs nextjs nextjs-boilerplate nextjs-example nextjs-starter nextjs-tailwind nextjs-template nextjs14 nextjs15 radix-ui shadcn shadcn-ui starter stripe t3-stack template

readme

Relivator 1.2.6: Next.js 15, React 19, TailwindCSS Template

We are currently migrating the documentation from the existing Relivator README.md to the official, newly launched Relivator & Reliverse Docs website (https://reliverse.org). The content will be organized into appropriate sections on the new site. During the migration, some elements might not function properly. The current README.md will contain only minimal information. Please let us know if you encounter any issues.

[🌐 Demo](https://relivator.com) | [πŸ‘‹ Introduction](#introduction) | [πŸ—οΈ Installation](#installation) | [🩷 Sponsors](#sponsors) [βš™οΈ Scripts](#scripts) | [πŸ€” FAQ](#faq) | [πŸ” Details](#details) | [βœ… Roadmap](#roadmap) | [πŸ“– Changelog](#changelog)

Stop jumping from one starter to the next. With Relivator, your possibilities are endless! You can create anything you want; all the tools are ready and waiting for you.

The entire Relivator project was developed by one person, Nazar Kornienko (blefnk)! Some people have already contributed, and you’re welcome to do the sameβ€”any contributions at all are appreciated! Your contributions will not be forgotten; our awesome community value them highly, and you might even receive financial gratitude from the project's creator in the future. Let's come together to create the most coolest Next.js template in the world! This will be a joint effort and a shared victory, a true win-win. Thank you all for your contributions and financial support!

Please take a moment to read through the information below. You'll find helpful details about how everything works in the project, as well as an extensive list of features.

Shows the landing page of Relivator Next.js template, with its logo and the phrase 'Relivator Empowers Your eCommerce with the Power of Next.js'. Dark-themed image displaying various technologies and tools used in the Relivator project. The heading highlights Next.js 15, React 19, shadcn, and Tailwind Template. The image is divided into multiple sections listing technologies like shadcn, tailwind, next 15, react 19, clerk, authjs, drizzle, neon, ts 5.6, python, eslint 9, ts-eslint 8, knip, biome, unjs, and reliverse. The background features a grid layout with a minimalistic design, inspired by the Figma and Loading UI style.

[![Discord chat][badge-discord]][link-discord] [![npm version][badge-npm]][link-npm] [![MIT License](https://img.shields.io/github/license/blefnk/relivator-nextjs-template.svg?color=blue)](LICENSE) [𝕏](https://x.com/blefnk) | [GitHub](https://github.com/blefnk) | [Slack](https://join.slack.com/t/reliverse/shared_invite/zt-2mq703yro-hKnLmsgbIQul0wX~gLxRPA) | [LinkedIn](https://linkedin.com/in/blefnk) | [Facebook](https://facebook.com/blefnk) | [Discord](https://discord.gg/Pb8uKbwpsJ) | [Fiverr](https://fiverr.com/blefnk)

Β«I couldn't find the sports car Next.js starter of my dreams, so I built it myself.Β» Β© Ferdinand Porsche @blefnk

Our goal is to create the world's most feature-rich and globally accessible Next.js starter. It offers more than just codeβ€”it's an experience. Scroll down to see the impressive list of project features, including the ability to switch between Clerk/Auth.js (next-auth@beta/NextAuth.js) and Drizzle's MySQL/PostgreSQL on the fly. Welcome to the Relivator starter and the Reliverse community!

Introduction

πŸ‘‰ Read the Detailed Blog Post About 1.2.6 & 1.3.0@canary Update πŸ‘ˆ

βœ… Relivator 1.2.6 uses the following dependencies (only some are listed): Next.js 15, React 19, TypeScript 5.5/5.6, Tailwind 3/4, tRPC 11, Clerk 5, Auth.js 5, ESLint 9 (with multiple plugins like typescript-eslint 8, react, unicorn, sonarjs, perfectionist, tailwindcss, readable-tailwind, import-x, jsx-a11y, security, markdown, mdx, json), Biome, Stripe, Million, Reliverse, next-intl, shadcn/ui, radix-ui, react-query, pnpm, zod, cn, turbo, Drizzle (Postgres, MySQL, SQLite, Neon, Railway, PlanetScale, Turso), GSAP, SWR, Resend, react-email, next-themes, Putout, Flowbite, Udecode, Slate, uploadthing, Radash, CSpell, TypeStat, Lucide & Radix Icons, Vercel & Loglib Analytics, Axios, Day.js, Embla Carousel, Execa, Math.js, UnJS libs (consola, fs-extra, pathe, etc), and much more

[upd. 18.08.2024] You can now try out the first published Reliverse Addon – @reliverse/fs, which is already available and used in Relivator! πŸŽ‰ The upcoming Relivator 1.3.0 will have as few dependencies as possible. Everything will work thanks to @reliverse/addons. Everything will be separated into its own libraries and will be published on npmjs and/or jsr. You will be able to install exactly what you need, including functionality and UI. You will have two options. One is to install the addons the classic way using 'package.json'. The other option is that all these addons can also be installed in a style inspired by shadcn/ui, where you keep all the content directly in your project (as it is currently in test mode in Relivator 1.2.6 (please check addons folder or run pnpm addons)), although the first option will be recommended for the most use cases. 'addons' folder already contains many cool things, especially related to codemods. It also includes the @reliverse/academy game, where you can check how good you know JavaScript/TypeScript, React/Next.js, Relivator/Reliverse, and even ESLint, ecosystems (you will even find there table of records and will can contest with other players if you share data/players.json and data/progress.json save files to them; the game has also achievement system).

πŸ™ Please help us reach 1,000 stars on GitHub: Once this project reaches this goal, I, @blefnk, the author of this project, will start my video course on the basics of web development (HTML, CSS, JS), React, Next.js, TypeScript, related libraries, and many other topics. This milestone will also affirm that Relivator and Reliverse truly make sense to exist, leading to more frequent updates and further dedication to these projects.

⭐ Bookmark this page in your browser: This project will only get better in the future. You can also click the star at the top of the page and add the repo to your collection to keep it easily accessible.

The Huge Relivator 1.2.6 & 1.3.0@canary are Already Available

πŸ‘‰ Read the Detailed Blog Post About 1.2.6 & 1.3.0@canary Update πŸ‘ˆ

Relivator 1.2.6 was released on August 4, 2024! We are now actively working on the next major update, Relivator 1.3.0, with the goal of making the project production-ready, clean, and high-quality. We invite you to join us in actively searching for issues, contributing freely, and earning cool rewards. A canary branch was launched a few days ago (and is available to everyone in the main repo), and the dev branch is also now available (the dev branch is available for a limited time to all sponsors at any paid pledge level).

πŸ”₯ Important Note: Relivator currently requires specifying Clerk environment variable keys, as its API has changed. We are working on making Clerk optional again. However, all other environment variables are optional. If this statement is incorrect and something is broken, please let us know.

What About the Future? Any News on 1.3.0?

πŸŽ‰ The upcoming Relivator 1.3.0 will have as few dependencies as possible! Finally!

I'm (blefnk) working to automate the Relivator's developer experience as much as possible, including the installation process. The upcoming version 1.3.0 will feature significant automated installation. If you wish to try the initial alpha version of one of my many automation scripts, use the pnpm deps:install (or pnpm deps:install-all) command. This script already allows you to install and remove project packages, and it also works as a linter. You can check the comprehensive number of predefined commands configured inside the 'scripts' section of the 'package.json' file. However, before running this script, you should manually install the essentials:

Thanks to @reliverse/addons, everything now works smoothly with fewer dependencies. In the future, each feature and component will be split into its own library and published on npmjs and/or jsr, so you can install only what you need. With the future Relivator 1.3.0 version, you won't have to deal with unnecessary components in web templates anymore. You get the core package and can add features and UI components as you need them.

The 'addons' folder is divided into two parts: terminal context and browser context (it's everything, excluding the 'addons/scripts' folder). The 'addons/scripts' folder contains functions used by the CLI (command line interface), while the 'src' and 'addons/*' folders (excluding 'addons/scripts') are for the browser, since the browser doesn't support certain JS features. So, while 'addons/scripts' has everything needed for the whole app, not everything can import from 'addons/scripts'.

You’ll have two installation options: the classic method using 'package.json' or a new approach inspired by shadcn/ui, where you keep all the content directly in your project (currently in test mode in Relivator 1.2.6β€”check the addons folder or run pnpm addons). While the classic method is recommended for most cases, feel free to explore the new approach!

The 'addons' folder is already packed with many exciting features, especially related to codemods, and includes the @reliverse/academy game. This game allows you to test your knowledge of JavaScript/TypeScript, React/Next.js, Relivator/Reliverse (make food/tea/coffee before trying this testβ€”it has a lot of questions!), and even ESLint v9 ecosystems. It features a leaderboard, enabling you to compete with others by sharing data/players.json and data/progress.json save files. Plus, an achievement system keeps you motivated!

I can’t wait for you to experience the new and improved Relivator 1.3.0! By the way, the items in the βœ… Roadmap section will finally be checked off! But to make 1.3.0 truly stable, production-ready, and just great, let's first work together on Relivator v1.3.0-canary.0, which is coming soon! If you want to get it even faster, there is now a 'dev' branch. We recently opened the project pages on financial support platforms, and currently, any contribution grants you access to the 'dev' branch. Thank you for your attention!

Sponsors

We're Growing Fast! A Huge Thanks to All Our Supporters!

Developing something as ambitious as Relivator takes a lot of time, especially since the project is primarily developed by just one person. The development could be significantly accelerated by hiring additional developers. Therefore, @blefnk (Nazar Kornienko), the author of this project, would be immensely grateful to anyone who can donate to the project in any amount. A big thank you to everyone in advance!

Visit the "Donate to Relivator" page to learn more.

Relivator is currently sponsored by the following awesome people/organizations:

πŸ’š GitHub Sponsors 🩡 PayPal 🧑 Patreon πŸ’› Buy Me a Coffee 🩷 Ko-fi

Love using this project? If you find this project useful, I'd appreciate a cup of coffee. You'll get Reliverse Pro, access to some private repositories, pre-release downloads, and the ability to influence my project planning. Please click on the donation platforms above to learn more. Thank you, everyone, for any kind of support!

I retrieve your data from donation and related platforms. If you do not wish for certain information about you to be included here, please contact me.

πŸ’œ Discord Server Boost

πŸ–₯️ Hire Me

Hello, I'm Nazar Kornienko, a flexible web developer specializing in JavaScript/TypeScript and React/Next.js front-end development. If you’re looking for someone with my skill set, please contact me at blefnk@gmail.com or via Discord.

Please explore the current repository to learn more about my experience with the JavaScript/TypeScript and React/Next.js ecosystems. I'm available for both remote work and full-time positions. While my primary focus is frontend and CLI development, if you need help with code automation tools, small tasks related to Python or backend, or even designs in Figma, graphic design, or copywriting/marketing, feel free to reach out to me as wellβ€”I’d love to see how I can assist.

🀝 Partnerships

Starting with version 1.2.6, Relivator is now truly production-ready. However, there's still much to be accomplished, and you might be surprised when you check the βœ… Roadmap section! To reach our goals, we are seeking partners to collaborate and support each other's projects' growth. If you're interested and would like to learn more, please feel free to email me at blefnk@gmail.com.

Our Partners

Gallery of all partners' logos

Railway

πŸ™ Dear Audience, I Need Your Help

Currently, I’m in a challenging financial situation, so I would greatly appreciate any recommendations or mentions of my work and Relivator as part of my portfolio, such as on the pages of your own repositories. Your support would mean a lot to me! As a token of my appreciation, I’d be happy to send some interesting gifts to you. Thank you for your time and consideration!

Installation

How to Install and Get Started: You have two options for installation. You can either immediately deploy to Vercel using the button below and start working on the generated repository right away (but still read the information below), or you can follow the short or detailed manual installation instructions provided.

By The Way: Sometimes, we gift Reliverse Pro, which gives you early access to the Reliverse projects ecosystem, including Relivator, as well as upcoming plugins, to randomly selected individuals. We also give away other interesting things. Simply star this repository and let us know how to reach you. To join the discussion, hop into the project's Discord.

One-click Installation Method (find recommended method below)

πŸ”₯ Important Note: Relivator currently requires specifying Clerk environment variable keys, as its API has changed. We are working on making Clerk optional again. However, all other environment variables are optional. If this statement is incorrect and something is broken, please let us know.

By using this method, you will get only the front-end, with all the functionality disabled (learn how to enable it by reading the manual instructions below):

Deploy with Vercel

Please note: As of version 1.2.6 and 1.3.0 (dev and canary), it is recommended to use Clerk as the authProvider (specified in the reliverse.config.ts file) since this version has been more thoroughly tested with Clerk. We are working on fixing and improving the stability of Auth.js (next-auth@beta/NextAuth.js) as an authentication provider.

Manual Installation: Short Method (find recommended method below)

πŸ”₯ Important Note: Relivator currently requires specifying Clerk environment variable keys, as its API has changed. We are working on making Clerk optional again. However, all other environment variables are optional. If this statement is incorrect and something is broken, please let us know.

  1. Node.js LTS: (A) classical method - Windows/macOS | Linux; (B) nvm - Windows | macOS/Linux; (C) fnm.
  2. Tools: corepack enable pnpm ➞ VSCode ➞ Git ➞ GitHub Desktop (Windows/macOS | Linux) ➞ Stripe CLI. Windows only: PowerShell 7.4+.
  3. Fork the repo: Download your fork using GitHub Desktop.
  4. Setup: pnpm install && install:global && pnpm reli:setup ➞ pnpm reli:vscode ➞ cp .env.example .env ➞ fill in the values inside of .env ➞ pnpm db:push ➞ reliverse.config.ts.
  5. Run, Build, Deploy: Use pnpm dev to run the app. Stop with Ctrl+C. Build with pnpm build. Run pnpm appts to check the code. Upload to GitHub with GitHub Desktop. Deploy on Vercel.

Manual Installation: Detailed Method (recommended)

πŸ”₯ Important Note: Relivator currently requires specifying Clerk environment variable keys, as its API has changed. We are working on making Clerk optional again. However, all other environment variables are optional. If this statement is incorrect and something is broken, please let us know.

β–² Hotline: Email | Discord | Slack | Cal.com

I'm (blefnk) working to automate the Relivator's installation process as much as possible. The upcoming version 1.3.0 will feature a significant automated installation. If you wish to try the alpha version of one of my many automation scripts, use the pnpm deps:install (or pnpm deps:install-all) command. However, before running this script, you should manually install the essentials (edit 'pnpm dlx jsr' if needed): npx nypm add typescript tsx @clack/prompts @mnrendra/read-package nypm ora fs-extra pathe fast-npm-meta semver @types/semver redrun && pnpm dlx jsr add @reliverse/core.

Please note: As of version 1.2.6 and 1.3.0 (dev and canary), it is recommended to use Clerk as the authProvider (specified in the reliverse.config.ts file) since this version has been more thoroughly tested with Clerk. We are working on fixing and improving the stability of Auth.js (next-auth@beta/NextAuth.js) as an authentication provider.

  1. Node.js LTS: Ensure you have Node.js LTS installed using: (a) classical method - Windows/macOS | Linux; (b) nvm - Windows | macOS/Linux; (c) fnm.
  2. Essential Tools: Then, run corepack enable pnpm to install pnpm. Also, install VSCode, Git, GitHub Desktop (Windows/macOS | Linux), and Stripe CLI. If you're a Windows user: install PowerShell 7.4+ as well.
  3. Project Cloning: Fork the repository or click on the Use this template button. Use GitHub Desktop to download it to your device. The project size is about 12MB, but ensure you have at least 7GB of disk space for comfortable work, as the node_modules and .next folders require it.
  4. Configuration: Open the project folder in VSCode. Install the recommended extensions from .vscode/extensions.json and/or install the advanced VSCode configurations by using pnpm reli:vscode (choose the default preset for the best experience or the ultimate preset for the best experience). You can also refer to the βš™οΈ Scripts and πŸ€” FAQ RQ19 below to learn more about this script and its configurations. You can press Cmd/Ctrl+F and search for "Q19/Q20" if you want to install more extensions and settings (remember, more extensions mean slower VSCode). Then click File > Exit (VSCode will save all your open windows). Open VSCode again. Press Ctrl+Shift+P (or just F1) and search for >Create New Terminal, or just press Cmd/Ctrl+Shift+~ (on Windows make sure that it uses PowerShell 7.4+, click the arrow next to + ➞ Select Default Profile ➞ PowerShell). If VSCode prompts you to allow the usage of the project's TypeScript version, allow it if you're a Windows user. On other operating systems, you may or may not encounter path issues.
  5. Environment: Run pnpm install (or npx nypm install) and/or, optionally, install:global to install the required packages. It is also recommended to configure reliverse.config.ts file. Then, optionally, you can use pnpm deps:install-allβ€”especially pnpm deps:install-all (this is currently an alpha script)β€”to unlock some additional features, like the eslint.config.ultimate.ts preset (which will have a .txt extension by default starting with Relivator v1.3.0). (NOTE: As of Relivator v1.2.6, the ultimate preset is configured by default, so no action is required). Next, configure Relivator to meet your needs using the pnpm reli:setup and/or pnpm reli:vscode commands, and relaunch VSCode. You have two options: deploy with zero values in the .env file (resulting in just the frontend without features related to auth, database, pricing, etc.), or copy the .env.example file to a new .env file and fill in the values you want (everything is optional starting with Relivator v1.2.6). It is highly recommended to fill in the DATABASE_URL field. Then, set the database provider in drizzle.config.ts and make changes in related files if needed. Finally, send the database schema to the database using pnpm db:push. You can learn more about databases below in the current README.md file.
  6. Run, Stop, Build: Run the app with pnpm dev or pnpm turbo:dev (interactive but unstable). Visit http://localhost:3000 to check it out. Stop it by focusing on the console and pressing Ctrl+C. After making changes, build the app using pnpm build or pnpm turbo:build. Don't worry if you see warnings related to Clerk, React Compiler, Babel, next-auth, etc. when running the build; these are known issues not related to Relivator. Note that when using the pnpm turbo:build command, the VSCode terminal may not exit automatically. If this happens, press Cmd/Ctrl+C to close the process manually.
  7. Check, Commit, Deploy: To check if the current codebase meets @reliverse/standard, run pnpm appts (or pnpm appts:noputout, or pnpm turbo:appts, or pnpm appts:nobuild). Learn more about project scripts in the next section. If everything is fine, upload the project to your GitHub profile using GitHub Desktop. Finally, deploy it by importing the project into Vercel, making the website publicly accessible on the internet. Alternatively, you can use pnpm deploy or just vercel to preview and inspect the local deployment without committing to GitHub every time.

It is recommended: From time to time, run pnpm reli:prepare. This script executes pnpm install, which checks for issues or installs/removes manually added/removed dependencies in your package.json file. It also executes pnpm latest, which installs the latest versions of project dependencies. Finally, it runs pnpm appts, which will do its best to improve your code and check for any errors. Note: Since pnpm latest updates all packages to their latest versions, be aware that something in the code might break, especially if considerable time has passed since the last version of Relivator was released. Therefore, you can use, for example, the VSCode extension Open Multiple Files to easily find and fix broken code, or reach out to the Relivator Discord server for assistance, or create a GitHub Issue. You can learn more about those scripts and the mentioned extension below in the current README.md file.

If you'd like to share your work, get/provide feedback, or ask for help, feel free to do so either in our Discord server or via GitHub discussions. Note: Currently, the instructions above may be outdated. Please contact us if something goes wrong; everything will be updated in Relivator 1.3.0.

🎢 Recommendation

Coding becomes a whole new experience with the right music, doesn't it? Enhance your workflow with Relivator and enjoy the soothing melodies from the MF Piano YouTube channel. This channel, run by my brother, offers beautiful piano covers that are perfect for background music. Your subscriptions, views, likes, and comments would mean the world to us and help his channel grow. Thank you for your support!

Scripts

The project includes various scripts designed to enhance your developer experience. You can run any script using your terminal. Please note that some CLI scripts may require you to adjust the height of your terminal window to avoid UI anomalies. The Relivator allows you to use the following:

  1. πŸ’ͺ Native Scripts: These are commands configured in package.json and run by the package manager like pnpm, bun, yarn, or npm. You can run these "native" scripts using commands like pnpm [dev|build] and pnpm db:[push|studio].
  2. βš™οΈ Custom-Built Scripts: These scripts are written in TypeScript and Python by Reliverse and the community and are mostly located in the addons folder. πŸ”₯ Please be cautious when using transformation scripts, as they are all in their initial versions. Ensure you commit your changes to your version control provider (such as GitHub) before using any of them. They can be executed via the command line using [appts|addons|reli|lint|fix]:* or manually via pnpm tsx path/to/file or py path/to/file (e.g., py addons/scripts/reliverse/relimter/python/tasks/math-to-mathjs.py).
  3. 🐍 Python Script Manager: Can be executed using reli:manager or py addons/scripts/reliverse/relimter/python/index.py. Before running it, please read the 🐍 Python section below to learn how to prepare your workspace to run this manager.

package.json

Below are some scripts configured in the scripts section of the package.json file (the following text may be outdated in some places, please let us know if you find any inaccuracies):

# pnpm tsx reliverse.config.ts --details
β„Ή β–² Framework: Relivator v1.2.6 β–² Engine: Reliverse v0.4.0 β–² Hotline: https://discord.gg/Pb8uKbwpsJ
β„Ή Relivator v1.2.6 Release Blog Post πŸ‘‰ https://reliverse.org/relivator/v126
β„Ή Help Relivator become even better! Please star the repo – https://github.com/blefnk/relivator
β„Ή For experienced users: run 'pnpm reli:prepare' to update all dependencies to the latest versions and check if the code requires any adjustments.
β„Ή Meet quality standards: run 'pnpm appts' and 'pnpm fix:putout-unstable' to get linting, formatting, and more.
β„Ή Unstable: try 'pnpm turbo:dev' and faster build with 'pnpm turbo:build': https://turbo.build/repo
β„Ή The reactCompiler is enabled in next.config.js - it uses webpack now, so builds take longer.
β„Ή Clerk: make sure to connect the domain in the Clerk dashboard so services like PageSpeed will work.
β„Ή Please find Q21 in the FAQ of README.md. Copy the adapted bun scripts and replace the current ones in package.json - scripts for other package managers coming soon.

Python

πŸ‘‹ Hello, dear friend! Nice to see you here! I (@blefnk Nazar Kornienko) have a dream of making the open-source world better and of higher quality. I aspire to leave my mark in history by ensuring people genuinely enjoy programming and create quality products. I'm particularly passionate about clean code. The book "Clean Code" by Robert Martin is a must-have!

That's why I've developed numerous tools in Relivator. Over the past few months leading up to Relivator 1.2.6, I've learned a lot. To avoid manually rewriting code, I've developed a unified script manager. The current version of the manager is still very unstable. You can visit the addons/scripts/reliverse/relimter/python/index.py file to learn more about how this script manager works.

If you want to use this Python Script Manager (refer to βš™οΈ Script to read the introduction), then please ensure your workspace is properly prepared for it. Please note that most scripts are largely untested. Commit your code before running any script. Increase your VSCode terminal window size to avoid UI glitches. Need help? Visit our Discord. Follow the steps below to get started (scroll down to learn even more Python commands):

βœ… After following the instructions above, you can safely run the script manager.

  1. Install Python and Ruff. Install the following VSCode extensions: Python and Ruff.
  2. Create a new .venv folder by pressing Cmd/Ctrl+Shift+P and running >Python: Create Environment... (VSCode will prompt you to choose the Python interpreter; choose the one installed in step 1). Then, choose requirements.txt as the package dependencies file.
  3. Please note, VSCode's terminal automatically activates the environment after each launch. You can verify this by hovering over a [pwsh|bash|cmd] button in VSCode's terminal and looking for something like "Python: Activated environment for .\.venv\Scripts\python.exe". However, if you are using another IDE or an external terminal, you may need to activate the virtual environment manually: [Windows] .venv/Scripts/activate; [macOS/Linux] source .venv/bin/activate.
  4. Ensure all requirement are installed correctly, just run pip install -r requirements.txt.

🐍 Everything ready? Nice! Congratulations! Try running the Python Script Manager now by executing: reli:manager or py addons/scripts/reliverse/relimter/python/index.py

Useful Python Commands

We are still working on this section. The following description may currently be slightly incorrect.

# - Install the required dependencies:
pip install -r requirements.txt

# - Make sure you have `pip-tools` installed to use `pip-compile` and `pip-sync`:
pip install pip-tools

# - You can create/update a `requirements.txt` file:
pip freeze > requirements.txt

# - Sync the dependencies:
pip-sync requirements.txt

# - Remove a specific package (e.g., torch):
pip uninstall torch
pip freeze > requirements.txt

Please note: If you have UV installed and you've used a command like uv pip install InquirerPy and it shows an error like "The wheel is invalid", the easiest solution is to just use regular pip commands like pip install InquirerPy.

FAQ

This is not only a Reliverse-specific FAQ but also a developers' FAQ for Next.js and the React ecosystem in general.

RQ29: Should I modify the components by shadcn/ui (as of Relivator 1.2.6, they are located in the "addons/components/ui" folder)? RA29: You may lose your changes if @shadcn or Reliverse updates any of these components in the release of Relivator 1.3.x+. Therefore, the best option currently is to use, for example, the "addons/cluster/reliverse/shadcn/ui" folder, where you can have files that you can safely overwrite the original files with, ensuring you do not lose your changes. As an example, this folder already contains a cluster-readme.tsx file, which only re-exports the original button.tsx file. So, you can create a button.tsx file here and copy and paste that line into your newly created file. Alternatively, you can duplicate the code from the original file and make any modifications you want. Use Cmd/Ctrl+Shift+H and simply replace addons/components/ui with addons/cluster/reliverse/shadcn/ui (the difference is only in the words "browser" and "cluster"). addons/cluster is your house; feel free to do anything you want here, mess it up or tidy it up as you wish. This is your own house, and no one has the right to take it away from you.

Details

🌐 https://relivator.com

Screenshot showing the main page of the Relivator project

We've laid the groundworkβ€”now it's time to dive in and accelerate development. And yeah, have fun! Think of Relivator and Reliverse as a sandbox! It's like Minecraft; with Relivator, you can build anything, as creativity knows no bounds! Explore all the new features of Next.js 13-15 and many other web technologies right here, right nowβ€”with Relivator.

Minecraft Reliverse is to a large degree about having unique experiences that nobody else has had. The levels website templates are randomly elegantly generated bootstrapped, and you can build anything you want to build yourself. Β© Markus Persson @blefnk

For real, if you've been exploring which Next.js starter to select for your next project–the search can end here. If you want a POWERHOUSEβ€”Relivator is suitable for every scenarioβ€”then Relivator is definitely the starter you need. Fork it right now! Relivator incorporates numerous features found in other templates and strives to push the limits of Next.js and React capabilities. With Relivator, the opportunities are boundless!

You can even think of Relivator as a Next.js framework! So grab it and enjoy! And don't forget: feedback and stars mean the world to us. Hit that star button! Fork it! Your involvement propels the project to new heights! If you have coding skills, contributions are always welcome!

If you run into issues, join our repository discussions, open an issue, or DM us on: Discord, Twitter/X, Fiverr, LinkedIn, or Facebook.

This project has big plans, and we appreciate all the help we can get! If you're eager to contribute, check out the Project Roadmap above to see potential improvements for the project. Also, use Cmd/Ctrl+Shift+F in VSCode and search for TODO: to find areas that need attention. Please visit the Issues tab for more opportunities to help out.

Project Structure

Only a few of the files are listed here. This section will be updated in the future versions.

Configuration

First thing first, refer to the .env.example file as the guide. Simply copy data from it to a new .env file.

The instructions below may be outdated, so please double-check them! We will fully update this README.md with the Relivator 1.3.0 release.

πŸŽ‰ Everything is optional in .env file starting from Relivator 1.2.6! You can deploy Relivator without a .env file! But ensure you verify what's necessary. Though the application will run without certain variables, missing ones may deactivate specific features.

Ensure that default values are defined for essential environment variables. Never store secrets in the .env.example file. For newcomers or repo cloners, use .env.example as a template to create the .env file, ensuring it's never committed. Update the schema in /src/env.js when adding new variables.

Further information about environment variables is available here.

A cleaner and improved version of this section is coming soon. Stay tuned!

In the 1.1.0 Relivator release, the .env.example file was greatly simplified and will be streamlined even further in upcoming versions. We aim to ensure that unspecified values will simply deactivate related functionality without halting app compilation.

Payments

Refer to the .env.example file as the guide for where and how to get all the important environment variable keys for Stripe, including webhooks for both localhost and deployment.

Locally, install the Stripe CLI and run the command pnpm stripe:listen to initiate the Stripe webhook listener. This action connects Stripe to the account and generates a webhook key, which you can then set as an environment variable in Stripe's settings.

When testing Stripe, you can use its test data: 4242424242424242 | 12/34 | 567 | Random Name | Random Country.

Please refer to the src/app/api/webhooks/stripe/route.ts file for more details on how Stripe works in the app. You can also visit the official Stripe repository, where you'll find a lot of useful information.

Database

Relivator uses Drizzle ORM for database management. By default, the project uses Neon (Serverless) with PostgreSQL as the database provider. The project has already followed Drizzle's guide on how to set up Drizzle with Neon Postgres.

August 4, 2024: Hot Update:

If you use neon as your database provider, you no longer need pnpm db:studio; simply use Drizzle Studio on Neon's website πŸŽ‰

For development databases without important data, you can use pnpm db:push. For production databases containing important data, it is recommended to use pnpm db:generate followed by pnpm db:migrate.

Drizzle Kit lets you alter you database schema and rapidly move forward with a pnpm db:push command. That’s very handy when you have remote databases like Neon, Planetscale or Turso. The 'push' command is ideal for quickly testing new schema designs or changes in a local development environment, allowing fast iterations without the overhead of managing migration files. Β© Drizzle Team

Drizzle Team: If you want to iterate quickly during local development or if your project doesn’t require migration files, Drizzle offers a useful command called drizzle-kit push. When do you need to use the β€˜push’ command? 1. During the prototyping and experimentation phase of your schema on a local environment. 2. When you are utilizing an external provider that manages migrations and schema changes for you (e.g., PlanetScale). 3. If you are comfortable modifying the database schema before your code changes can be deployed.

Note: NEXT_PUBLIC_DB_PROVIDER was removed in Relivator v1.2.6. To switch the provider from Neon, modify drizzle.config.ts. To use MySQL or LibSQL providers, update the files inside src/db. An automatic switcher is coming in Relivator version 1.3.x.

The instructions below may be outdated, so please double-check them! We will fully update this README.md with the Relivator 1.3.0 release.

Relivator is designed to effortlessly support both MySQL and PostgreSQL databases. While PostgreSQL and Neon are the default configurations, switching to MySQL provided by Railway or PlanetScale, or to PostgreSQL provided by Railway or Vercel is straightforward. Adjust the database configuration inside drizzle.config.ts and the src/db/* files accordingly. Although Relivator is optimized for these providers, other providers compatible with Drizzle and Auth.js (next-auth@beta/NextAuth.js) might also work with some additional setup. Full SQLite support is coming soon.

To set up the DATABASE_URL in the .env file, refer to .env.example. Initiate a new database or propagate schema changes by executing the pnpm db:push command. This ensures that all changes made to the schema files in src/db/* are mirrored in the selected database provider.

For database migrations, use the pnpm db:generate command, review the drizzle folder to ensure everything is correct, and run the pnpm db:migrate command when ready. If necessary, use pnpm db:drop to manage reversals in a controlled way.

If you used Relivator before v1.2.6, you may remove the drizzle folder inside the root directory. Possible outdated information: Do not manually delete files from the drizzle directory. Instead, use the pnpm db:drop command if a migration needs to be reversed.

We ensure consistent database configuration by using the setup inside drizzle.config.ts and exporting configurations in src/db/index.ts and src/db/schema/index.ts. When selecting a database provider, comment out or remove unneeded providers in the switch-case of these files and remove related schema files as necessary. Additional adjustments in other files may also be required. An automatic switcher is coming soon in the Relivator v1.3.0 release.

Historical context: In Relivator v1.1.0, we aimed to provide simultaneous support for both MySQL and PostgreSQL for Drizzle ORM. In future releases, we plan to integrate Prisma ORM, making the project even more inclusive.

Product Categories and Subcategories

To edit product categories, please refer to the MySQL, PostgreSQL, or LibSQL corresponding schema file in the src/db/schema folder.

After editing these files, don't forget to run pnpm db:push to apply the changes. Or run pnpm generate to create a sharable SQL, which another developers may apply with pnpm migrate to edit theirs database tables easily.

Then, simply update the category names and subcategories in the products file accordingly.

Additional Notes About Stripe

The instructions below may be outdated, so please double-check them! We will fully update this README.md with the Relivator 1.3.0 release.

The Stripe webhook API route does not need to be invoked explicitly within the application, such as after a user selects a subscription plan or makes a purchase. Webhooks operate independently of user actions on the frontend and serve as a means for Stripe to relay events directly to the server.

When an event occurs on Stripe's end, such as a successful payment, Stripe generates an event object. This object is then automatically sent to the endpoint you've specified, either in the Stripe Dashboard or, for testing purposes, in the package.json via the Stripe CLI. Finally, the server's API route receives the event and processes it accordingly.

For example, when a user selects a subscription plan, you would typically first use Stripe's API to create either a Payment Intent or Setup Intent object. This action can be executed either on the client-side or the server-side. The frontend then confirms the payment using Stripe.js, thereby completing the payment or subscription setup process.

The webhook is automatically triggered based on these events. There's no need to manually "call" the webhook route; Stripe manages this for you according to the settings in the Stripe Dashboard or in the package.json for local testing.

After deploying the app, don't forget to specify the webhook URL in the Stripe Dashboard. Navigate to the Webhooks section and enter the following URL: https://thedomain.com/api/webhooks/stripe.

In summary, there's no need to specify the path to the Stripe API route where the user selects a subscription plan. The webhook mechanism operates independently and is triggered automatically by Stripe.

Internationalization

Stay tuned for further expansions to this section in the future.

The instructions below may be outdated, so please double-check them! We will fully update this README.md with the Relivator 1.3.0 release.

Multilingualism at Bleverse Reliverse vision is revered. We adore discussing it and plan to delve into the topic of Next.js 15 App Router internationalization in future writings.

Presently, all languages are machine-translated. Future revisions by native speakers are planned.

useTranslations works both on the server and client; we only need the getTranslations on async components.

Currently not available. Use pnpm lint:i18n to verify the i18n files. The tool attempts to rectify issues when possible, offering features like ascending sort. No output means everything is in order.

We are using next-intl for internationalization. Sometime we can use beta/rc versions as needed. Find more information about it here and here.

How to add a new language

The process described below will be simplified and automated in the future. Please let us know if you have any further questions regarding the current process for adding languages.

  1. We will need an i18n code (in the format language-country; the language code alone is sufficient, but it's not optimal for SEO). For example, let's take Chinese, for which I know the codes zh-cn/zh-tw/zh-hk are used.
  2. Open the messages folder and create a zh-cn.json file with the example content: { "metadata": { "description": "ε»Ίη«‹ζ›΄ι«˜ζ•ˆγ€ζ›΄εΈεΌ•δΊΊδΈ”ζ›΄ζœ‰εˆ©ε―ε›Ύηš„εœ¨ηΊΏε•†εΊ—οΌšδ½Ώη”¨ Relivator" } }.
  3. Now open src/i18n.ts and add "zh-cn": zh_cn with the appropriate import at the top.
  4. In the file src/navigation.ts, add the corresponding values to locales and labels.
  5. Run pnpm dev and review the landing page header. If it appears correctly, you're ready to go.
  6. Optionally, I recommend using the VSCode extension i18n Ally, which makes machine translation easy.
  7. Also optionally, install specific CSpell language for full support of this language in VSCode (when using the "Code Spell Checker" extension). If the language is not available, try to find a word dictionary file on the web or make a new one (see CSpell docs).

By the way, if the country flag is not displayed: open src/localization-main.tsx, go to LocaleFlagIcon and add the else if. Please visit the flag-icons library website to see the code for the missing icon. The example for zh-cn will be: } else if (baseLocale === "zh") { return <span aria-hidden="true" className="fi fi-cn mr-2" />; }

Please be aware that both the "i18n Ally" VSCode extension and manual systems like "Google Translate" may incorrectly translate variables. If you encounter an error like this: Original Message: 'The intl string context variable "类别" was not provided to the string "θ΄­δΉ°ζœ€ε₯½ηš„{类别}"'. This error occurs because we have {类别}, but it should be {category}. To verify the correct variable, refer to the en-us.json file.Certainly! So the correct version for this specific case will be:

{
  "categories": {
    "buyFromCategories": "δ»Žζœ€ε₯½ηš„商店购买 {category}",
    "buyProducts": "θ΄­δΉ° ${category} η±»εˆ«ηš„δΊ§ε“",
    "buyTheBest": "θ΄­δΉ°ζœ€ε₯½ηš„ {category}"
  }
}

Currently supported locales (you can add the own manually):

Principles, Design Decisions, Code Insights, Recommendations

Β«There are a lot of impractical things about owning a Porsche Relivator. But they're all offset by the driving experience. It really is unique. Lamborghinis create-t3-app and Ferraris Vercel Store come close. And they are more powerful in specific cases, but they don't handle like a Porsche Relivator.Β» Β© Kevin O'Leary @blefnk

We're continuously improving this section. Contributions are welcomed!

Our starter aims to be a rich resource for developers at all stages of their journey. Within the comment blocks and dedicated sections at the end of select files, you'll find valuable insights and clarifications on a wide array of topics. Contributions to enhancing these educational nuggets are highly encouraged!

Principles (W.I.P):

Advanced Environment Variables:

The .env.example file covers all the essential variables for a fully functional website, tailored for beginners. However, if you require advanced configurations, you can modify any value in the .env file as needed.

About the Plugins Folder:

This folder contains optional plugins for Relivator. Developed by @blefnk and other contributors, these plugins extend functionality and provide additional features. If you find that certain plugins are not beneficial for the project, feel free to remove their corresponding folders.

Function Over Const for Components:

We advocate the use of the function keyword instead of const when defining React components. Using function often improves stack traces, making debugging easier. Additionally, it makes code semantics more explicit, thereby making it easier for other developers to understand the intentions.

Personal Recommendations:

We advise regularly clearing the browser cache and deleting the .next folder to ensure optimal performance and functionality.

Currently, we don’t utilize Contentlayer due to its instability with Windows. Therefore, we're exploring options for its usage in the .env configuration file. Future plans might involve developing our own solution for content writing. Integration with external providers, such as Sanity, may also be a future feature, with corresponding enable/disable options.

NOTE from the Contentlayer Issues Page: Contentlayer doesn't work well with next.config.mjs, so you need to have next.config.js. Other libraries may also require this. If you're sure you need .mjs and don't plan to use Contentlayer, rename it.

Project Configuration:

The src/app.ts file hosts main configurations to modify website contents and settings, enabling you to:

Customize this file as per the requirements.

Authentication:

Setting up authentication is straightforward.

You can configure available sign-in providers for Clerk in the src/app.ts file.

Please remember that Clerk fully works with third-party services like "Google PageSpeed Insight" only when domain and live keys are used.

This section will be implemented soon.

TypeScript Config:

In the tsconfig.json file you can set the options for the TypeScript compiler. You can hover over on each option to get more information about. Hint: You can also press Shift+Space to get auto-completion. Learn more by checking the official TypeScript documentation: @see https://typescriptlang.org/docs/handbook/tsconfig-json @see https://totaltypescript.com/tsconfig-cheat-sheet.

Next.js has built-in support for TypeScript, using plugin below. But while you use pnpm build, it stops on the first type errors. So you can use pnpm typecheck to check all type warns/errors at once.

Config includes Atomic CSS plugin in the style attribute. Type-safe static styles with theming, responsive variant support, and no bundler integration. @see https://github.com/tokenami/tokenami#readme.

You can enable strict type checking in MDX files by setting mdx.checkMdx to true.

These options below can be dangerously set to false, while you're incrementally move to full type-safety.

{
  "alwaysStrict": true,
  "noImplicitAny": false,
  "strict": true,
  "strictNullChecks": true,
  "strictPropertyInitialization": true,
  "verbatimModuleSyntax": true
}

How to Deploy the Project:

Please check the How to Install and Get Started section before making the initial deployment.

Consult the deployment guides for Vercel, Netlify, and Docker for further details. The project has only been tested on Vercel; please inform us if you encounter issues with other deployment services.

Styling, Design System, UI Components:

TODO: Implement design system and style guide.

By default, this project includes components from various libraries, as well as unstyled shadcn/ui components. Shadcn/ui even allows you to generate new UI components using its CLI (where "button" can be any Shadcn UI element): pnpm dlx shadcn-ui@latest add button.

W.I.P. β€” Use pnpm css to watch for CSS tokens in accordance with the project's design system. Tokenami and Figma are anticipated to be utilized for this concept. For additional information, refer to points #33 and #90 in the Relivator's Roadmap.

Package Manager Compatibility:

Relivator can already harness some fantastic Bun features. For this starter, we currently recommend using pnpm. Full pnpm support and compatibility will be shipped as soon as Reliverse's Versator achieves full similarity with Relivator. Section expansion coming soon.

Recommended Things to Learn:

  1. The Detailed Git Guide by Nazar Kornienko @Blefnk
  2. Introduction to Next.js and React by Lee Robinson
  3. Relivator: Next.js 15 Starter (Release Announce of Relivator on Medium) by Nazar Kornienko @Blefnk
  4. Welcome to the Wild World of TypeScript, Mate! Is it scary? by Nazar Kornienko @Blefnk
  5. React: Common Mistakes in 2023 by Cory House
  6. Thoughts on Next.js 13, Server Actions, Drizzle, Neon, Clerk, and More by @Apestein
  7. Huge Next-Multilingual Readme About i18n by @Avansai
  8. Applying Design Principles in React by Jeremiah (Jerry) Ezekwu
  9. The Power of Prototyping Code by JoΓ£o Miguel Cunha
  10. Software Prototyping on Wikipedia
  11. TDD: Test-driven development on Wikipedia
  12. React 19 RC Announcement by React

More learning resources can be found within the files of this repository.

Contributing

This section will be enhanced soon with simpler steps to get everything ready.

Contributions are warmly welcomed! We express our gratitude to everyone who has contributed to this repository. the contributions will be recognized. If you have any questions or suggestions, please open an issue. For more information, see the contributing guide.

Please visit this special wiki page to view the full list of credits and contributors. To contribute to Relivator, follow these steps:

  1. Begin by reading the "How to Install and Get Started" section on the top of this repository, and by reading CONTRIBUTING.md page.
  2. Create a branch: git checkout -b <branch_name>.
  3. Make and commit the changes: git commit -m '<commit_message>'
  4. Push to the original branch: git push origin <branch_name>
  5. Submit the pull request.

Alternatively, check the GitHub docs on how to create a pull request.

Roadmap

The roadmap below may be outdated. We will fully update this README.md with the Relivator 1.3.0 release.

The roadmap below outlines the key features and improvements planned for this Next.js Reliverse starter and for Reliverse CLI. Items not marked may already be configured but might not have been thoroughly tested. If you spot any issues, please open an issue.

[Join the Relivator Discord][badge-discord]

License

This project is licensed under the MIT License and is free to use and modify for your own projects. Please visit the license file for details. Since this project is under a free license, the author reserves the right to include referral links. The author may receive compensation from these links if users follow them and, for example, pay their first bill. Thank you all for your understanding!

🌐 https://relivator.com

Changelog

a.k.a. What's Happening?!

1.2.6 - August 4, 2024 – The Resurrection Update

Below you can see a small copy of the article from Reliverse Docs, which is possibly outdated. Please refer to 1.2.6 Release Notes Page on GitHub or to this blog post to read the most recent version. Reliverse Docs also has translations of the article into other languages; and will contain even more information about Relivator than this README.md, including notes from all past and future releases.

Relivator is Back with Version 1.2.6! πŸ₯³

We are excited to announce the release of Relivator 1.2.6! This version marks the end of the "all-in-one" approach as we prepare for a more modular future with Reliverse CLI starting from version 1.3.0. The 1.2.6 release includes significant updates, especially in the database logic. The README.md has been significantly updated. Moving forward, we will introduce Canary, Release Candidate (RC), and General Availability (GA) branches for better version management. 1.2.6 will serve as a foundation, helping us transition more smoothly to the release of those 1.3.0's branches.

Major Changes and Improvements

Migration Guidance

Starting from version 1.3.1, we will provide comprehensive guides for migrating from older versions. The usual migration process involves reviewing commit changes and integrating necessary updates into your custom code. However, due to the extensive changes in versions 1.2.6 and 1.3.0, this method is not feasible. We recommend reinstalling the project and transferring your custom features from the previous version to the new version of starter. Thank you for your understanding!

To make the migration as smooth as possible, it's recommended to create a "cluster" folder in "src" and moving all your custom code there. If needed, you can adjust the paths using the Find and Replace feature in VSCode. This will make it much easier to save and transfer your custom code to Relivator 1.2.6.

Default Database Change

Neon PostgreSQL is now the default database instead of PlanetScale MySQL, as the latter no longer offers a free tier. If you require MySQL, Railway offers a more affordable alternative with a $5 credit without requiring a credit card. Note that this version has been primarily tested with Neon PostgreSQL.

Security and Code Improvements

Reliverse Scripts Transition

Reliverse scripts have moved from the "unknown viability" stage to the "unstable" stage. As always, use them at your own risk and make backups. These scripts are now located in the addons/relimter/[core|python] folder. Most scripts require Python to be installed.

For more details on this update, you can read my detailed posts in the Relivator thread on Discord. Start with this message.

Thank You So Much

If anyone have any questions or issues, don't hesitate to contact me, means @blefnk, on Discord or GitHub. For more information about 1.2.6 and 1.3.0, please visit #⭐-relivator chat on the project's Discord server and the GitHub Issues page.

Thank you for your continued support and happy coding with Reliverse Website Builder v0.4.0 and Relivator Next.js Template v1.2.6!

Release Notes 1.2.5-1.0.0

This is what happened before 1.2.6 version:

v1.2.5 β€” 27.02.2024 Hello! I, @blefnk Nazar Kornienko, finally have the opportunity to get back to working on Relivator after a month of exams at university. Thanks to all the new starter users! The project already has over 520 stars, 110 forks, 20 repository watchers, and 45 users in Discord - that's really cool and exciting! I also want to thank the active Discord users of the project: *codingisfun, el_ade, righthill, nyquanh, spacecoder315, adelinb*. Thank you to everyone who creates PR/Issues and everyone else who actively uses the starter, whose nicknames I don't know. Your feedback and contributions are incredibly valuable for the development of the project! Since there hasn't been an update in over a month, I'm going to make the transition to the next major version smoother. Therefore, version 1.2.5 has been released to simply refresh the dependencies and other minor details and README a bit. This small update will also allow me to check if certain users continue to have the individual strange problems they reported. If everything goes well, the next update will already be version 1.3.0. By the way, I'm working on 1.2.x and 1.3.0 in parallel, like in big studios, haha. But please note: some files and lines of code was disabled by default for this version to fix and check some things. By the way, the third digit means that this update is not mandatory, but still recommended. And Relivator 1.3.0 may or may not come with a canary version of React/Next.js to start preparing for the upcoming release of React 19. Well, that's all for today, all the best to everyone, and may your `pnpm latest` and `pnpm appts` always be successful! As usual, I try to write a short announcement, but it turns out a few paragraphs, that's how we live! πŸ˜„ P.S. And, please, don't pay attention that so many files have been "changed" in the latest commit, looks like it's because of Prettier I think, I only updated a few files, and if it's important to someone, please let me know in Discord's DM and I'll list you these files. [Read more about v1.2.5](https://github.com/blefnk/relivator-nextjs-template/releases/edit/1.2.5)
v1.2.4 β€” 13.01.2024 Just a small hotfix to improve the developer experience. [Read more about 1.2.4](https://github.com/blefnk/relivator-nextjs-template/releases/edit/1.2.4)
v1.2.3 β€” 12.01.2024 Just a small hotfix to improve the developer experience. [Read more about 1.2.3](https://github.com/blefnk/relivator-nextjs-template/releases/edit/1.2.3)
1.2.2 β€” 03.01.2024 1.2.2 brings ESLint Stylistic Plugin into the life. This will make the work with the project even more enjoyable. Remember, Relivator is designed to be beginner-friendly, so quite a lot of ESLint options are turned off, just turn on what you need. These turn-offs will be gradually eliminated as we move towards the massive 2.0.0, which will significantly raise the project's standards, being professional, will be even more convenient for beginners. [Read more about v1.2.2](https://github.com/blefnk/relivator-nextjs-template/releases/edit/1.2.2)
1.2.1 β€” 02.01.2024 This is quite a small update compared to all the past ones, but this one also deserves the attention. Now, updates will generally be smaller but will appear more frequently. Thanks to this, it will be possible to easily update forks and independent projects that use Relivator as their base. Update v1.2.1 adds Chinese localization, and among other things, work has begun on the so-called token system, which will allow future versions to work with Figma design systems in an automated way. It will also help to make the styles in the project cleaner by significantly reducing the number of Tailwind classes. For this, Relivator now installs the wonderful package @tokenami, developed by @jjenzz; Jenna, thank you so much for this library! p.s. 1.2.1 is the first commit to the Relivator repository that no longer contains an emoji at the beginning of its name. Thanks to this, contributors to Relivator/Reliverse will no longer have to spend time inventing a suitable emoji. [Read more about v1.2.1](https://github.com/blefnk/relivator-nextjs-template/releases/edit/1.2.1)
1.2.0 β€” [27.12.2023] πŸŽ„ Relivator v1.2.0 is here! πŸ₯³ Click to see the announcement 🎁 *Relivator 1.2.0 is already here! I, [@blefnk Nazar Kornienko](https://github.com/blefnk), am thrilled to wrap up this year 2023, proudly presenting this release to the OSS community! So, the result of over two months of hard work is finally here!* In this version, significant attention was focused on stability, security, performance optimization, and a substantial improvements in designβ€”both visually, UX, and the logic of how the app works. A lot was really done, too much to list everything! Be sure to install it and check it out! By the way, you can now enjoy a finely-tuned ESLint Flat Config! Also, it's worth noting that Clerk, since version 1.1.0, is no longer considered deprecated in the Relivator project. Thanks to 1.2.0, Clerk now works seamlessly with an easy switch to Auth.js (next-auth@beta/NextAuth.js) when needed, all on the fly. Plus, full support for Turbopack (next dev --turbo) is finally here, even for next-intl! As for next-intl, finally, we can now enjoy internationalization that works not only on the client-side but also on the server! Only the 404 page has client-side i18n messages, all other pages and components use i18n as server-first. And this is really cool! Many unique solutions have been implemented in this new version. Moreover, using Relivator from this version, you have the opportunity to try out the alpha version of our unique Code-First/No-Code Builder system for React pages and components (which will appear in Reliverse CMS in the future). Just visit the Admin page while in the development environment and enjoy. If you have already used Relivator before, please pay attention, this is very important! Be sure to check the updated .env.example file and update the .env file accordingly. As a small teaser/spoiler, for Relivator 1.3.0, even more improvements in visual design and UX are planned; 1.4.0 will come with a magical CLI implementation, allowing you to quickly obtain only the necessary features and dependencies for the app (even automated updates and the ability to add other functions and packages to an already installed app); 1.5.0 will undergo a full code refactoring that will meet all the best standards and practices; 1.6.0-2.0.0+ versions, apart from many other things, will receive most of the items currently unchecked in the Roadmap (located in the project's README.md). It's going to be incredible! So, install this new version of Relivator 1.2.0 and appreciate the multitude of incredible features, and freely use it in the own projects today. Please use the preferred feedback channels to share the thoughts on Relivator 1.2.0 and what you would like to see in future releases. Don't forget to also check out the significantly updated README.md, it's worth it. Enjoy! β„οΈβ˜ƒοΈ Merry Christmas and Happy New Year 2024! πŸŽ‡πŸ₯³
1.1.0 β€” πŸ”₯ The Most Feature-Rich Next.js 15 Starter Here it is! Relivator has been updated to version 1.1.0! **Now it's even more feature-rich, with cleaner code, and a more stable Next.js starter.** Ever dreamed of having both MySQL/PostgreSQL and Clerk/Auth.js (next-auth@beta/NextAuth.js) in one project with the ability to switch on the fly? And even if you hadn't thought about it – now it's possible. Mix and match at will – even more possibilities for on-the-fly switching are coming soon in the next releases of Relivator. Among many other new and fixed things, Stripe is now fully functional and comes with extensive docs in the form of comments within the relevant files. `Please star this repository` to show the support! Thank you to everyone who has shown interest in this project! Please check out the updated list of project features in the project's README. Enjoy and please share the feedback! [Read more about v1.1.0](https://github.com/blefnk/relivator-nextjs-template/releases/edit/1.1.0)
1.0.0 β€” πŸŽ‰ Relivator Release How to Install and Get Started? Please refer to the [πŸ—οΈ Installation](#installation) section, where you can always find information about the project and how to install it easily. [Read more about v1.0.0](https://github.com/blefnk/relivator-nextjs-template/releases/tag/1.0.0)

Please visit the CHANGELOG.md or Reliverse Docs to read the release notes for older versions.

The Final Words

This Next.js 15 starter β€” Relivator β€” was crafted with love by @blefnk Nazar Kornienko and the incredible Bleverse OSS community. We are deeply grateful for all your contributions and support for this project.

Happy coding! Embark on the coding adventure, learn, iterate, and most importantly – enjoy the process! Remember – this is a space of learning and experimentation. Dive in and savor the journey! πŸš€πŸŒŒ

Check out our other free Next.js 15 starter. This monorepo provides the tech used in the current starter and adds: Turborepo/Turbopack, Prisma, Valibot, Lucia, Clerk, and much more, as we experimentally attempt to combine all vital and widely-used tech. Think of it as: Reliverse (WordPress) + Relivator (WooCommerce) = 😍. So, start right now! Start today with Relivator!

Reliverse

> πŸš€ **Ready to launch?** Start building your project with Relivator and Reliverse as soon as possible! With one-click deploy on Vercel: [![Deploy with Vercel](https://vercel.com/button)](https://vercel.com/new/clone?repository-url=https%3A%2F%2Fgithub.com%2Fblefnk%2Frelivator-nextjs-template&project-name=relivator&repository-name=my-new-repository-name) > πŸ’» **Prefer manual installation?** Refer to the [πŸ—οΈ Installation](#installation) section or just clone the project using the most classical way: ```bash git clone https://github.com/blefnk/relivator.git ``` [2023-2024 Β© Nazar Kornienko / Nazar Kornienko / blefnk](https://github.com/blefnk) ()

Relivator OG Image

[![Join the Relivator Discord](https://discordapp.com/api/guilds/1075533942096150598/widget.png?style=banner2)][badge-discord] [🌐 Demo](https://relivator.com) | [πŸ‘‹ Introduction](#introduction) | [πŸ—οΈ Installation](#installation) | [πŸ€” FAQ](#faq) | [πŸ” Details](#details) | [βœ… Roadmap](#roadmap) | [πŸ“– Changelog](#changelog) **Follow Us Everywhere:** [𝕏](https://x.com/blefnk) | [GitHub](https://github.com/blefnk) | [LinkedIn](https://linkedin.com/in/blefnk) | [Facebook](https://facebook.com/blefnk) | [Discord](https://discord.gg/Pb8uKbwpsJ) | [Fiverr](https://fiverr.com/blefnk) [badge-discord]: https://badgen.net/discord/members/Pb8uKbwpsJ?icon=discord&label=discord&color=purple [badge-npm]: https://badgen.net/npm/v/reliverse?icon=npm&color=green&label=%40blefnk%2Freliverse [link-discord]: https://discord.gg/Pb8uKbwpsJ [link-npm]: https://npmjs.com/package/reliverse/v/latest