Shipped
HomeContacts
  • Get started
  • 📚Tutorials
    • Make a waiting list
    • Launch a pre-sale
    • Build a SaaS
    • Create your store on Lemon Squeezy
  • 🟩Features
    • AI Services
    • Affiliate Program
    • Analytics
    • Authentication
      • MailChimp
      • Loops
      • AWS SES
      • SendGrid
      • Supabase Auth
        • Supabase Authentication Flow
        • Supabase Magic Link
        • Supabase Email & Password
        • Supabase Login with Google
    • API endpoints
      • 🛡️Authenticated API
    • Blog
    • Customer support
    • Chrome Extension
    • Dark mode
    • Database
      • Update your database
      • MongoDB
    • Emails
    • Error pages
    • Icons
    • Onboarding
    • Payments
      • Lemon Squeezy
        • Subscriptions
        • One-time purchase
        • Test mode
      • Stripe
    • Private pages
    • SEO
    • shadcn/ui
    • Supabase
    • Workspace / Organizations
  • 📦Components
    • AccountMenu
    • CtaBox
    • DarkModeSwitch
    • Explainer video
    • FAQ
    • Features
    • Footer
    • Header
    • Hero
    • Lifetime
    • Pricing
    • Sales Notification
    • Secondary Sidebar Pages
    • Sidebar
    • Tabs
    • Testimonials
    • Waitlist
    • WebAppPage
  • 🚀Deployment
  • ✅Other
    • Configuration
    • Changelog widget
    • Favicon
    • Google Fonts
    • Sitemap
    • Theme
  • Updates
  • GitHub Repository
  • Support
Powered by GitBook
On this page
  • Configuration
  • NodeJS Version

Was this helpful?

Get started

Get started in 5 minutes

Welcome to Shipped, the NextJS boilerplate to launch your SaaS in days!

Shipped code is on GitHub, so start by forking the repo.

If you have purchased the Startup package go to this page and click on the Fork button:

https://github.com/ShippedBoilerplate/shipped

If you have purchased the Startup + Chrome Extension package go to this page and click on the Fork button:

https://github.com/ShippedForBrowserExtensions/shipped-browser-extensions

In the fork form, select the owner (your GitHub user), uncheck the option "Copy the main branch only", and click on Create fork.

Why forking?

When you create a fork, you own the new repository, while your fork keeps a link to the original repository.

This means that if I update the Shipped boilerplate code, you can integrate the latest changes with the click of a button.

In your repository, you will find a button on GitHub called "Sync Fork" that allows you to integrate the changes I make in the original repository at any time!

Now it's time to clone the forked repository.

Go to your forked repository on GitHub, click on the "Code" button, and select "Open with GitHub Desktop" for the easiest way to download the repository to your local computer.

Instead, if you're familiar with the git CLI, use the command git clone git@github.com:<your fork>.

Finally open a terminal, go to the folder you cloned the repository into, and run:

terminal
cp .env.example .env # copy the env file
npm i # install the dependencies
npm run dev # start the local next.js server

Point your browser to that page, and see it in action! 🚀

Pretty exciting, right?!

Configuration

NodeJS Version

To correctly run Shipped, you need to use the version of NodeJS 20.10.0

To enforce it, the repository includes a .nvmrc file.

To activate the correct NodeJS version, go to the Shipped folder and run

terminal
nvm install 20.10.0
nvm use

Common next steps:

NextMake a waiting list

Last updated 4 months ago

Was this helpful?

At this point, your product is running at

Check the page to configure your web app (mandatory for most of the features).

NVM is the Node Version Manager that you can download .

Pro tip Install the when you move to a folder with a .nvmrc file.

Configure a

Configure

http://localhost:3000
Configuration
here
script to automatically switch nodejs version
database
authentication