README.md

Starter

A fullstack cross-platform template using:

• Next.js
• Prisma
• GraphQL (Apollo)
• Capacitor
• Ionic (based on )
• Storybook

Automatic CRUD API, GraphQL API and types generated from Prisma.

It's like a very opinionated variant of RedwoodJS.

🚀 Quickstart (Web)

Install Node.js (between 16.10.0 and 17.0.0)

Install Yarn (v1.22.19 or higher)

Install dependencies and start development:

yarn
yarn dev

📱 iOS and Android

Setup Capacitor for iOS or Android (or both) Build the mobile apps:

yarn mobile-build

Open the iOS app in Xcode:

npx ionic cap run ios -l --external

Open the Android app in Android Studio:

npx ionic cap run android -l --external

Docs

Before the Storybook is ready for deployment, you can view the docs locally by starting development and visiting http://localhost:6006/ (should happen automagically with the script).

Why aren't all the docs available in the README?

Some of the docs is very interactive and running everything live locally.

TODOs

• Automatically adjust URLs to work in development both locally and in cloud environments (e.g. GitHub Codespaces and CodeSandbox Projects)
• Support styled-components' css-prop when using SWC with StoryBook
  • The css-prop is currently the only thing holding us back from using SWC with StoryBook
  • StoryBook supports the css-prop now, but uses Babel instead of SWC:

    module.exports = {
      <!-- ... -->
      babel: {
        plugins: [["babel-plugin-styled-components", styledConfig]],
      }
      <!-- ... -->
    };

  • Preferably make Next.js' styled-components support work with SWC and StoryBook
  • We're using a Next-addon for StoryBook, but it's seemingly not supporting SWC
  • Why even use SWC?
    • It's many times faster than Babel
    • Vercel's reasoning for using SWC for Next.js
    • Same behavior between StoryBook and Next.js
• Address yarn dev warnings
• Improve MDX integration
  • Get css-prop to work
  • Better type checking
  • Better IntelliSense
  • Markdown tooling feature parity for VSCode
• More intuitive way of using TypeGraphQL-classes in the client
  • For example: SomeExampleModel.prototype will return undefined, even though TypeScript promises a result
  • A shim-fix has been implemented (see prisma/browser-shim.ts and webpack-configs), but it only stops the build from crashing. The user can still try to get data from the server, but the types are wrong.