Simple TODO app using the Next.js React framework.

This application is meant to be some kind of boilerplate for me to learn about the various tools used in web development.

https://github.com/nvm-sh/nvm/blob/master/README.md

curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.0/install.sh | bash

Run the built application in production mode

Build container image using the Containerfile in folder postgresql:

$ podman run -d --rm --name postgres -p 15432:5432/tcp postgresdb:latest

$ psql -h localhost -p 15432 -U testuser -d testdb

Build on different versions of Node.js locally (example)

$ nvm ls $ nvm use v16.14.2 $ npm ci $ npm run build --if-present

DATABASE_URL=postgresql://<username>:<password>@<database server URL>:5432/<database name>

NEXTAUTH_URL=https://example.com/api/auth

NEXTAUTH_SECRET that can be generated using $ openssl rand -base64 32

CORS_ALLOWED_ORIGIN to set the HTTP header Access-Control-Allow-Origin to something else than *

A twitter clone built with Next.js, Tailwindcss and Firebase.

You can start editing the page by modifying pages/index.js. The page auto-updates as you edit the file.

. This endpoint can be edited in pages/api/hello.js.

The pages/api directory is mapped to /api/*. Files in this directory are treated as 

 to automatically optimize and load Inter, a custom Google Font.

To learn more about Next.js, take a look at the following resources:

 - your feedback and contributions are welcome!

The easiest way to deploy your Next.js app is to use the 

frontend for flashcard app built in next.js

Challenge página de E-commerce con HTML, CSS y JavaScript | Programa ONE - Oracle Next Education.

Audio Gear Shop - Built with Next.js and SCSS (WIP)

uber clone-app in next.js

The all-in-one starter kit for high-performance SaaS applications.

Secure user management and authentication with 

Powerful data access & management tooling on top of PostgreSQL with 

Automatic syncing of pricing plans and subscription statuses via 

The Vercel deployment will guide you through creating a Supabase account and project. After installing the Supabase integration, you'll need to configure Stripe with a few simple steps.

 We're working on our Stripe integration. We've documented the required steps below under "Configure Stripe" until the integration is ready.

Once the project has deployed, continue with the configuration steps below.

The initial build will fail due to missing Stripe environment variables. After configuring Stripe, redeploy the application.

Setup redirect wildcards for deploy previews

For auth redirects (magic links, OAuth providers) to work correctly in deploy previews, navigate to the auth settings (i.e. https://app.supabase.com/project/:project-id/auth/url-configuration) and add the following wildcard URL to "Redirect URLs": https://**vercel.app/*/*.

You can read more about redirect wildcard patterns in the 

You can use third-party login providers like GitHub or Google. Refer to the 

 to learn how to configure these. Once configured you can add them to the provider array of the Auth component on the 

To start developing your SaaS application, we'll need to configure Stripe to handle test payments. For the following steps, make sure you have the 

We need to configure the webhook pictured in the architecture diagram above. This webhook is the piece that connects Stripe to your Vercel Serverless Functions.

Set the endpoint URL to https://your-deployment-url.vercel.app/api/webhooks.

Click Select events under the Select events to listen to heading.

Click Select all events in the Select events to send section.

Copy Signing secret as we'll need that in the next step.

To securely interact with Stripe, we need to add a few 

 in Stripe. The STRIPE_WEBHOOK_SECRET_LIVE is the Signing secret copied in the previous webhook configuration step.

We need to redeploy the application so that the latest environment variables are present.

Redeploy your application by going to the deployments tab, finding your deployment, and clicking "redeploy."

For Stripe to automatically bill your users for recurring payments, you need to create your product and pricing information in the 

. When you create or update your product and price information, the changes automatically sync with your Supabase database.

Stripe Checkout currently supports pricing that bills a predefined amount at a specific interval. More complex plans (e.g., different pricing tiers or seats) are not yet supported.

For example, you can create business models with different pricing tiers, e.g.:

 fixtures command executes a series of API requests defined in a JSON file. To speed up the setup, we have added a 

 to bootstrap test product and pricing data in your Stripe account. Simply run stripe fixtures fixtures/stripe-fixtures.json.

 Be sure to start the webhook forwarding (see below) so that the products created by the fixtures command above are imported into your database.

Toggle on "Allow customers to update their payment methods"

Toggle on "Allow customers to update subscriptions"

Toggle on "Allow customers to cancel subscriptions"

Add the products and prices that you want

Set up the required business information and links

Generate types from your Supabase database

 to generate types from your Database by running

npm install supabase --save-dev yarn add supabase --dev

Enter your access token. You can generate an access token from 

npx supabase gen types typescript --project-id [YOUR-PROJECT-REF] --schema public > types_db.ts

That's it. Now you're ready to earn recurring revenue from your customers 🥳

Archive all test mode Stripe products before going live. Before creating your live mode products, make sure to follow the steps below to set up your live mode env vars and webhooks.

Configure production environment variables

To run the project in live mode and process payments with Stripe, modify the environment variables from Stripe "test mode" to "production mode." After switching the variables, be sure to redeploy the application.

To verify you are running in production mode, test checking out with the 

Afterward, you will need to rebuild your production deployment for the changes to take effect. Within your project Dashboard, navigate to the "Deployments" tab, select the most recent deployment, click the overflow menu button (next to the "Visit" button) and select "Redeploy."

Deploying with Vercel will create a repository for you, which you can clone to your local machine.

Use the Vercel CLI to download the development env vars:

Running this command will create a new .env.local file in your project folder. For security purposes, you will need to set the SUPABASE_SERVICE_ROLE_KEY manually from your 

 (Settings > API). Lastly, the webhook secret differs for local testing vs. when deployed to Vercel. Follow the instructions below to get the corresponding webhook secret.

stripe listen --forward-to=localhost:3000/api/webhooks

Running this Stripe command will print a webhook secret (such as, whsec_***) to the console. Set STRIPE_WEBHOOK_SECRET to this value in your .env.local file.

Install dependencies and run the Next.js client

npm install npm run dev # or yarn yarn dev

Clone, deploy, and fully customize a SaaS subscription application with Next.js.

music streaming app with next.js

You can start editing the page by modifying pages/index.tsx. The page auto-updates as you edit the file.

. This endpoint can be edited in pages/api/hello.ts.

Repor pembuat aplikasi movie untuk test menggunakan next tailwindcss & typescript

Curso Profesional de Next

An iMessage-App built using Next.js with Typescript, GraphQL, Node.js, Prisma & MongoDB

A advance clone of digikala includes products page, single product page, category, sorting, filtering, JWT authentication, login page, register page, edit user information, order cart, review and admin dashbord to add new product, accept reviews, add category, details and specification for category and more...

Digikala Clone NextJs

Next.js, React.js, TypeScript, TailwindCSS, NextAuth, Redux

The Tesla application is a fully-featured web application that allows users to experience the latest and greatest of Tesla's cutting-edge vehicles. Built with Next.js, React.js, TailwindCSS, NextAuth, Redux, and TypeScript, this application provides a seamless and user-friendly experience for Tesla enthusiasts and car shoppers alike.

The Next.js framework provides server-side rendering capabilities, optimizing the application's performance by reducing the time it takes for pages to load. React.js is used to build the application's UI, providing a modular and reusable component-based approach to building UI elements. TailwindCSS is utilized to provide a simple and efficient way of styling the application, providing a comprehensive set of utility classes that can be easily customized.

NextAuth provides secure authentication and authorization capabilities for the application, allowing users to easily create and manage their accounts. Redux provides a centralized state management solution, allowing for efficient state updates across the application.

Finally, TypeScript is utilized to provide strong typing capabilities and ensure a clean and maintainable codebase. With all these technologies working in tandem, the Tesla application provides a modern and cutting-edge experience for Tesla fans and car shoppers alike.

https://tesla-clone-ilywdd3c8-beniaminav.vercel.app/

Tesla Clone with  Next.js, React.js, TypeScript, TailwindCSS, NextAuth, Redux

Walmart clone with next.js

Amzon Clone with React - Next.js - TypeScript - Redux - Firebase - TailwindCss

Amazon Clone with React - Next.js - TypeScript - Redux - Firebase - TailwindCss

reddit clone in next.js 13

imdb clone build with next js and tailwind

LinkTreez is a linktree clone made using Next.js 13, Tailwind, and Daisy UI.

 LinkTreez is using Next 13's expiremental app directory.

git clone https://github.com/engageintellect/linktreez.git

A linktr.ee clone using Next.js 13 w/ experimental app directory.

This is a clone of cowrywise built with next.js, scss and gsap

Generate a full static production buildyarn build

A simple clone of Netflix built with React, Next.js, Tailwind CSS and Prisma

A simple clone of Twitter built with React, Next.js, Tailwind CSS and Prisma

Search exercises by name, body part, muscle target or equipment

you get videos on how to do that exercise

you get similar exercises of that target muscle

you get similar exercises that you can do with the same equipment

Get 3 daily meals all planned out based on the amount of calories that you input

Get macronutrients info for your generated meals

You're able to see servings, prep time and recipe details

To get a local copy up and running follow these simple example steps.

Recommended to use pnpm for better experience, but npm or yarn works for the commands below too.

Install all dependencies using: - npm install.

React components that are used for specific pages, the ones that are generic are placed inside the shared folder.

Main screen components like Home & MealPlanning are added here.

Runs the app in the development mode.
Open 

The page will reload when you make changes.

Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.

Fit Healthy Sesh(Session) - A fitness app which shows exercises and plans meals for you

new sonnylab.com website built with Next.js, React Three Fibre, and Tailwind with Twin Macro

Navigate into your new site’s directory and start it up.cd sonnylab.com/ yarn yarn dev

Your site is now running at http://localhost:8080!

website built with Next.js, React Three Fiber, and Tailwind CSS with Twin Macro

This project is built with HTML5, CSS, Tailwind, React (ES6), and Next Js. The form data will be sent to the FormSpree API for collection.

Only one background image at tablet and mobile size

All pages will reuse the following components:

Tailwind - only used for general styling like margin and padding

The organization of the styles.css will be(in descending order):

A three page website, built with Next Js, React, Tailwind, and HTML5.

design portfolio to showcase a few projects. Built with 

Personal Website (Next.js, Three.js and Framer Motion)

This work is my new portfolio site built with 

. A website presents a single page application with carousel consisting of sections presented in the header.

To run this project locally, you need to have 

git clone https://github.com/Domin-MND/portfolio . # clone the repository into the current directory npm install # for the dependencies installation npm run build # for the production build npm start # start the server

npm i -g vercel # install the Vercel CLI tool vercel # deploy the project

You can configure the project by editing the config.tsx files in the following components:

components/about/config.tsx (for the About card)

components/contact/config.tsx (for the Contact card)

components/footer/config.tsx (for the footer component)

components/header/config.tsx (for the header component)

components/skills/config.tsx (for the Skills card)

components/works/config.tsx (for the Works card)

This project supports i18n. If no translation is provided to the language - it will take the config information from the above tsx files. The english default translation folder must be named en and should never be deleted but may be modified.

All the available documentation regarding the creation & maintainability of the project is in docs folder.

Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.

Huge thanks to these wonderful people for their contributions:


Translated portfolio to polish & helped with testing the web

Note: If you wish to help translate the portfolio to your language, please join the 

 license. You can freely use it for your own purposes.

A personal portfolio built with Next.js, Three.js & Mantine

This project is a web3 sandbox proof of concept, that allows users to purchase digital worlds in the form of NFTs, build upon them using 3D rendered blocks, and share those worlds inside of a metaverse that is saved to the blockchain.

The block-building gameplay aspect of this project was adapted from 

The proof of concept utilizes an in-game cryptocurrency, called MBlox, which faciliates the purchasing of different digital blocks for users to build with and the worlds in which they build.

The project is also playable without any web3 knowledge or integration; there is a "Sandbox" mode available from the Main Menu which allows a user to build within a provided digital world with an infinite number of blocks without the need of any web3 wallet connection or crypto balance of any kind.

This project was also deployed using Vercel (referenced in the stack above), and is available to play at the following address: 

NOTE: This project is a proof of concept, and not intended to represent a polished Web3 application. The contract system used in this application has not been audited, and I take no responsiblity for any issues that may arise out of its extended use.

There are four main aspects of gameplay within the project. These are as follows:

This aspect of gameplay allows users to convert their Polygon Mumbai Matic into the in-game currency (MBlox) to use within the game.

Alternatively, if the user has previously played by 

 and has earned the in-game METR token of that game with the wallet they have connected to this project, they will be able to claim a lump sum of MBlox equal to the difference their last claim and their current claim, (e.g. if they are claiming for the first time, the user can claim their entire METR balance as MBlox, and if they play METARANGERS since then and claim more METR since then, they can claim the new METR they have earned as MBlox)

This area of the project is where players can exchange their MBlox for the MetaBlox token, which represents the different blocks that can be used to build within the worlds of the game

The different variations of blocks that are available to the user are Dirt, Grass, Glass, Wood, Log, Lava, Gold, Opal, Amethyst, and Space.

As described earlier, this aspect of game allows the player to enter a digital world (equivalent to one of the worlds of the game) and build whatever they desire within it with an unlimited number of blocks at their disposal.

Players are unable to save anything that they create within the Sandbox to the blockchain, as this mode is intended to be an avenue of gameplay available to Web2 users.

This aspect of gameplay allows user to either purchase new worlds to build in, build in said purchased worlds, visit other user's individual worlds, or visit the MetaGrid itself, which is a vast digital world in which all one hundred available worlds within the project and rendered and laid out before the user, which they can explore in its entirety.

The different worlds are laid out in a grid of tiles, with coloured tiles represent worlds that are already purchased by users, and black tiles representing unclaimed worlds available for purchase.

This proof of concept uses a smart contract system that includes four implementations and seven interfaces. All the contracts were deployed to the 

, were written in the Solidity programming language and deployed using Hardhat, both of which are referenced in the stack displayed above. The implementations used in this smart contract system are as follows:

This contract represents the in-game currency that is primarily used to purchase the other tokens in the game.

 that provides basic minting and burning functionality.

This contract represents the different blocks that the user is able to purchase and then use to build with within the game.

, that contains balances for each of the variants of blocks as described above, the prices of each block in MBlox, and minting, burning, and batch minting and burning functionality.

This contract represents the different worlds that users can purchase and build within the game.

, that includes URI storage and burning functionality.

This contract facilitates interactions between the game and smart contract system.

 and includes several key aspects of functionality, including getter functions for retrieving values relevant to the game, enabling users to purchase other tokens within the MBlox in-game currency, and handling changes to world tokens that users make by placing and removing blocks.

The Game Manager also restricts the minting and burning capability of the other contracts in the system to actions that occur in the game, to prevent malicious users from attempting to mint or burn tokens outside of the context of the game. This is primarily facilitated through the use of a "digitalKey" variable that is required to call any functions that pertain to major functionality.

A 3D Minecraft-style Web3 game made with Next.js, Three.js, and Solidity

3D Text-Animation with Three.js, NextJs, Typescript

Next.js-powered Jamstack blog. It contains the source code, content, and configuration for the blog. It also includes some easter eggs, as a Wordle game 📕

Next.js-powered Jamstack blog

❗ This project is still in the early stages of development and should be considered unstable. Expect bugs and weird behavior.

spectate and chat in ongoing games with other users

 user accounts for tracking stats and game history (wip)

Built with Next.js 13, Tailwind CSS + daisyUI, react-chessboard, chess.js, Express.js, socket.io and PostgreSQL.

This project is structured as a monorepo using npm workspaces, separated into three packages:

client - Next.js application for the front-end, deployed to 

server - Node/Express.js application for the back-end, deployed to 

types - Shared type definitions for the client and server.

# install all dependencies, including eslint and prettier for development npm install # concurrently run frontend and backend development servers npm run dev # -w client/server to run only one # for separate production deployments npm install -w client npm install -w server npm run build -w client npm run build -w server npm start -w client npm start -w server

For separate deployments, you may exclude the client or server directory. However, you should include the types folder as it contains shared type definitions that are required by both packages.

You may create a .env file in each package directory to set their environment variables.

NEXT_PUBLIC_API_URL=http://localhost:3001 # replace with backend URL

CORS_ORIGIN=http://localhost:3000 # replace with frontend URL PORT=3001 SESSION_SECRET=randomstring # replace for security # PostgreSQL connection info (required) PGHOST=db.example.com PGUSER=exampleuser PGPASSWORD=examplepassword PGDATABASE=chessu

Next.Js Example

Next.Js Example

Next.Js Example

Next.Js Example

Categories

Technologies