feat(create-cedar-app): Create ESM apps

__fixtures__/fragment-test-project/.redwood/README.md

@@ -14,24 +14,24 @@ You don't need to commit any other contents of this directory to your version co
 
 ### Files
 
-| Name              | Description |
-| :---------------- | :------- |
-| commandCache.json | This file contains mappings to assist the Redwood CLI in efficiently executing commands. |
-| schema.graphql    | This is the GraphQL schema which has been automatically generated from your Redwood project. |
-| studio.db         | The sqlite database used by the experimental `rw exp studio` feature. |
+| Name              | Description                                                                                                        |
+| :---------------- | :----------------------------------------------------------------------------------------------------------------- |
+| commandCache.json | This file contains mappings to assist the Redwood CLI in efficiently executing commands.                           |
+| schema.graphql    | This is the GraphQL schema which has been automatically generated from your Redwood project.                       |
 | telemetry.txt     | Contains a unique ID used for telemetry. This value is rotated every 24 hours to protect your project's anonymity. |
-| test.db           | The sqlite database used when running tests. |
+| test.db           | The sqlite database used when running tests.                                                                       |
 
 ### Directories
 
-| Name        | Description |
-| :---------- | :------- |
-| locks       | Stores temporary files that Redwood uses to keep track of the execution of async/background tasks between processes.  |
-| logs        | Stores log files for background tasks such as update checking. |
-| prebuild    | Stores transpiled JavaScript that is generated as part of Redwood's build process. |
+| Name        | Description                                                                                                                                      |
+| :---------- | :----------------------------------------------------------------------------------------------------------------------------------------------- |
+| locks       | Stores temporary files that Redwood uses to keep track of the execution of async/background tasks between processes.                             |
+| logs        | Stores log files for background tasks such as update checking.                                                                                   |
+| prebuild    | Stores transpiled JavaScript that is generated as part of Redwood's build process.                                                               |
 | telemetry   | Stores the recent telemetry that the Redwood CLI has generated. You may inspect these files to see everything Redwood is anonymously collecting. |
-| types       | Stores the results of type generation. |
-| updateCheck | Stores a file which contains the results of checking for Redwood updates. |
+| types       | Stores the results of type generation.                                                                                                           |
+| updateCheck | Stores a file which contains the results of checking for Redwood updates.                                                                        |
+| studio      | Used to store data for `rw studio`                                                                                                               |
 
 We try to keep this README up to date but you may, from time to time, find other files or directories in this `.redwood` directory that have not yet been documented here. This is likely nothing to worry about but feel free to let us know and we'll update this list.
 

__fixtures__/fragment-test-project/.vscode/settings.json

@@ -7,5 +7,11 @@
   },
   "[prisma]": {
     "editor.formatOnSave": true
-  }
+  },
+  "tailwindCSS.classAttributes": [
+    "class",
+    "className",
+    "activeClassName",
+    "errorClassName"
+  ]
 }

__fixtures__/fragment-test-project/README.md

@@ -1,11 +1,6 @@
 # README
 
-Welcome to [RedwoodJS](https://redwoodjs.com)!
-
-> **Prerequisites**
->
-> - Redwood requires [Node.js](https://nodejs.org/en/) (=20.x) and [Yarn](https://yarnpkg.com/)
-> - Are you on Windows? For best results, follow our [Windows development setup](https://redwoodjs.com/docs/how-to/windows-development-setup) guide
+Welcome to your new [CedarJS](https://cedarjs.com) project!
 
 Start by installing dependencies:
 
@@ -20,103 +15,3 @@ yarn redwood dev
 ```
 
 Your browser should automatically open to [http://localhost:8910](http://localhost:8910) where you'll see the Welcome Page, which links out to many great resources.
-
-> **The Redwood CLI**
->
-> Congratulations on running your first Redwood CLI command! From dev to deploy, the CLI is with you the whole way. And there's quite a few commands at your disposal:
->
-> ```
-> yarn redwood --help
-> ```
->
-> For all the details, see the [CLI reference](https://cedarjs.com/docs/cli-commands).
-
-## Prisma and the database
-
-Redwood wouldn't be a full-stack framework without a database. It all starts with the schema. Open the [`schema.prisma`](api/db/schema.prisma) file in `api/db` and replace the `UserExample` model with the following `Post` model:
-
-```prisma
-model Post {
-  id        Int      @id @default(autoincrement())
-  title     String
-  body      String
-  createdAt DateTime @default(now())
-}
-```
-
-Redwood uses [Prisma](https://www.prisma.io/), a next-gen Node.js and TypeScript ORM, to talk to the database. Prisma's schema offers a declarative way of defining your app's data models. And Prisma [Migrate](https://www.prisma.io/migrate) uses that schema to make database migrations hassle-free:
-
-```
-yarn rw prisma migrate dev
-
-# ...
-
-? Enter a name for the new migration: › create posts
-```
-
-> `rw` is short for `redwood`
-
-You'll be prompted for the name of your migration. `create posts` will do.
-
-Now let's generate everything we need to perform all the CRUD (Create, Retrieve, Update, Delete) actions on our `Post` model:
-
-```
-yarn redwood generate scaffold post
-```
-
-Navigate to [http://localhost:8910/posts/new](http://localhost:8910/posts/new), fill in the title and body, and click "Save".
-
-Did we just create a post in the database? Yup! With `yarn rw generate scaffold <model>`, Redwood created all the pages, components, and services necessary to perform all CRUD actions on our posts table.
-
-## Frontend first with Storybook
-
-Don't know what your data models look like? That's more than ok—Redwood integrates Storybook so that you can work on design without worrying about data. Mockup, build, and verify your React components, even in complete isolation from the backend:
-
-```
-yarn rw storybook
-```
-
-Seeing "Couldn't find any stories"? That's because you need a `*.stories.{tsx,jsx}` file. The Redwood CLI makes getting one easy enough—try generating a [Cell](https://redwoodjs.com/docs/cells), Redwood's data-fetching abstraction:
-
-```
-yarn rw generate cell examplePosts
-```
-
-The Storybook server should hot reload and now you'll have four stories to work with. They'll probably look a little bland since there's no styling. See if the Redwood CLI's `setup ui` command has your favorite styling library:
-
-```
-yarn rw setup ui --help
-```
-
-## Testing with Jest
-
-It'd be hard to scale from side project to startup without a few tests. Redwood fully integrates Jest with both the front- and back-ends, and makes it easy to keep your whole app covered by generating test files with all your components and services:
-
-```
-yarn rw test
-```
-
-To make the integration even more seamless, Redwood augments Jest with database [scenarios](https://redwoodjs.com/docs/testing#scenarios)  and [GraphQL mocking](https://redwoodjs.com/docs/testing#mocking-graphql-calls).
-
-## Ship it
-
-Redwood is designed for both serverless deploy targets like Netlify and Vercel and serverful deploy targets like Render and AWS:
-
-```
-yarn rw setup deploy --help
-```
-
-Don't go live without auth! Lock down your app with Redwood's built-in, database-backed authentication system ([dbAuth](https://redwoodjs.com/docs/authentication#self-hosted-auth-installation-and-setup)), or integrate with nearly a dozen third-party auth providers:
-
-```
-yarn rw setup auth --help
-```
-
-## Next Steps
-
-The best way to learn Redwood is by going through the comprehensive [tutorial](https://redwoodjs.com/docs/tutorial/foreword) and joining the community (via the [Discourse forum](https://community.redwoodjs.com) or the [Discord server](https://discord.gg/redwoodjs)).
-
-## Quick Links
-
-- Stay updated: read [Forum announcements](https://community.redwoodjs.com/c/announcements/5), follow us on [Twitter](https://twitter.com/redwoodjs), and subscribe to the [newsletter](https://redwoodjs.com/newsletter)
-- [Learn how to contribute](https://redwoodjs.com/docs/contributing)

__fixtures__/fragment-test-project/api/package.json

@@ -1,10 +1,11 @@
 {
   "name": "api",
+  "type": "module",
   "version": "0.0.0",
   "private": true,
   "dependencies": {
-    "@cedarjs/api": "7.0.0",
-    "@cedarjs/auth-dbauth-api": "7.0.0",
-    "@cedarjs/graphql-server": "7.0.0"
+    "@cedarjs/api": "0.0.5",
+    "@cedarjs/auth-dbauth-api": "0.0.5",
+    "@cedarjs/graphql-server": "0.0.5"
   }
 }

__fixtures__/fragment-test-project/api/src/directives/requireAuth/requireAuth.test.ts

@@ -1,6 +1,6 @@
 import { mockRedwoodDirective, getDirectiveName } from '@cedarjs/testing/api'
 
-import requireAuth from './requireAuth'
+import requireAuth from './requireAuth.js'
 
 describe('requireAuth directive', () => {
   it('declares the directive sdl as schema, with the correct name', () => {

__fixtures__/fragment-test-project/api/src/directives/requireAuth/requireAuth.ts

@@ -1,9 +1,9 @@
-import gql from 'graphql-tag'
+import { gql } from 'graphql-tag'
 
 import type { ValidatorDirectiveFunc } from '@cedarjs/graphql-server'
 import { createValidatorDirective } from '@cedarjs/graphql-server'
 
-import { requireAuth as applicationRequireAuth } from 'src/lib/auth'
+import { requireAuth as applicationRequireAuth } from 'src/lib/auth.js'
 
 export const schema = gql`
   """

__fixtures__/fragment-test-project/api/src/directives/skipAuth/skipAuth.test.ts

@@ -1,6 +1,6 @@
 import { getDirectiveName } from '@cedarjs/testing/api'
 
-import skipAuth from './skipAuth'
+import skipAuth from './skipAuth.js'
 
 describe('skipAuth directive', () => {
   it('declares the directive sdl as schema, with the correct name', () => {

__fixtures__/fragment-test-project/api/src/directives/skipAuth/skipAuth.ts

@@ -1,4 +1,4 @@
-import gql from 'graphql-tag'
+import { gql } from 'graphql-tag'
 
 import { createValidatorDirective } from '@cedarjs/graphql-server'
 

__fixtures__/fragment-test-project/api/src/functions/auth.ts

@@ -3,8 +3,8 @@ import type { APIGatewayProxyEvent, Context } from 'aws-lambda'
 import { DbAuthHandler } from '@cedarjs/auth-dbauth-api'
 import type { DbAuthHandlerOptions, UserType } from '@cedarjs/auth-dbauth-api'
 
-import { cookieName } from 'src/lib/auth'
-import { db } from 'src/lib/db'
+import { cookieName } from 'src/lib/auth.js'
+import { db } from 'src/lib/db.js'
 
 export const handler = async (
   event: APIGatewayProxyEvent,

__fixtures__/fragment-test-project/api/src/functions/graphql.ts

@@ -5,9 +5,9 @@ import directives from 'src/directives/**/*.{js,ts}'
 import sdls from 'src/graphql/**/*.sdl.{js,ts}'
 import services from 'src/services/**/*.{js,ts}'
 
-import { cookieName, getCurrentUser } from 'src/lib/auth'
-import { db } from 'src/lib/db'
-import { logger } from 'src/lib/logger'
+import { cookieName, getCurrentUser } from 'src/lib/auth.js'
+import { db } from 'src/lib/db.js'
+import { logger } from 'src/lib/logger.js'
 
 const authDecoder = createAuthDecoder(cookieName)
 

__fixtures__/fragment-test-project/api/src/graphql/produces.sdl.ts

@@ -51,4 +51,4 @@ export const schema = gql`
       @skipAuth
     deleteProduce(id: String!): Produce! @skipAuth
   }
-`
+`;

__fixtures__/fragment-test-project/api/src/graphql/stalls.sdl.ts

@@ -26,4 +26,4 @@ export const schema = gql`
     updateStall(id: String!, input: UpdateStallInput!): Stall! @requireAuth
     deleteStall(id: String!): Stall! @requireAuth
   }
-`
+`;

__fixtures__/fragment-test-project/api/src/lib/auth.ts

@@ -1,7 +1,7 @@
 import type { Decoded } from '@cedarjs/api'
 import { AuthenticationError, ForbiddenError } from '@cedarjs/graphql-server'
 
-import { db } from './db'
+import { db } from './db.js'
 
 /**
  * The name of the cookie that dbAuth sets

__fixtures__/fragment-test-project/api/src/lib/db.ts

@@ -5,17 +5,22 @@ import { PrismaClient } from '@prisma/client'
 
 import { emitLogLevels, handlePrismaLogging } from '@cedarjs/api/logger'
 
-import { logger } from './logger'
+import { logger } from './logger.js'
 
-/*
- * Instance of the Prisma Client
- */
-export const db = new PrismaClient({
+const prismaClient = new PrismaClient({
   log: emitLogLevels(['info', 'warn', 'error']),
 })
 
 handlePrismaLogging({
-  db,
+  db: prismaClient,
   logger,
   logLevels: ['info', 'warn', 'error'],
 })
+
+/**
+ * Global Prisma client extensions should be added here, as $extend
+ * returns a new instance.
+ * export const db = prismaClient.$extend(...)
+ * Add any .$on hooks before using $extend
+ */
+export const db = prismaClient

__fixtures__/fragment-test-project/api/src/services/contacts/contacts.test.ts

@@ -6,8 +6,8 @@ import {
   createContact,
   updateContact,
   deleteContact,
-} from './contacts'
-import type { StandardScenario } from './contacts.scenarios'
+} from './contacts.js'
+import type { StandardScenario } from './contacts.scenarios.js'
 
 // Generated boilerplate tests do not account for all circumstances
 // and can fail without adjustments, e.g. Float.
@@ -39,7 +39,9 @@ describe('contacts', () => {
   })
 
   scenario('updates a contact', async (scenario: StandardScenario) => {
-    const original = (await contact({ id: scenario.contact.one.id })) as Contact
+    const original = (await contact({
+      id: scenario.contact.one.id,
+    })) as Contact
     const result = await updateContact({
       id: original.id,
       input: { name: 'String2' },

__fixtures__/fragment-test-project/api/src/services/contacts/contacts.ts

@@ -1,6 +1,6 @@
-import type { QueryResolvers, MutationResolvers } from 'types/graphql'
+import type { QueryResolvers, MutationResolvers } from 'types/graphql.js'
 
-import { db } from 'src/lib/db'
+import { db } from 'src/lib/db.js'
 
 export const contacts: QueryResolvers['contacts'] = () => {
   return db.contact.findMany()

__fixtures__/fragment-test-project/api/src/services/contacts/describeContacts.scenarios.ts

@@ -0,0 +1,12 @@
+import type { Prisma, Contact } from '@prisma/client'
+
+import type { ScenarioData } from '@cedarjs/testing/api'
+
+export const standard = defineScenario<Prisma.ContactCreateArgs>({
+  contact: {
+    one: { data: { name: 'String', email: 'String', message: 'String' } },
+    two: { data: { name: 'String', email: 'String', message: 'String' } },
+  },
+})
+
+export type StandardScenario = ScenarioData<Contact, 'contact'>