[ ] First, I disabled hoisting in the Remix starter package.json. This way, the "remix" binary is installed at the package level to avoid any issue: https://github.com/yarnpkg/yarn/issues/4964. This doesn't affect other packages or starters. This not optimal though, we'd like to find a way to hoist but keep "remix" CLI and critical deps in the right folder.
[ ] We have a message "Missing the "remix" package. Please run npm install remix before remix setup." on postinstall => this is probably normal at this point, since we have the same issue in raw Indie stack.
[ ] The "remix init" command is only run with "create-remix"! Not on "postinstall"! So you need to run it manually when cloning the monorepo => added some info in the readme, but we must double check a clean install of "vulcan-npm". I suspect remix.init folder packages are not installed automatically either, so we need first a "cd remix.init && npm installand thenyarn run remix init`.
This init script is for instance in charge of copying ".env.example" to ".env"
[ ] "yarn run dev" doesn't work, because "run-p" is probably not run at the correct level. ./node_modules/.bin/run-p dev:* does work though. Same for "yarn run build". => concurrently actually have the same features and should work better, to be testedhttps://www.npmjs.com/package/concurrently => Remix might also update to other better maintained tools
[ ] Maybe I should remove this starter from Yarn workspaces, however I am afraid this would later be problematic when importing local Vulcan packages (basically Yarn will fetch them on NPM, not link them locally)?
[ ] Investigate caching => no client-side GraphQL also means no Apollo cache. We purely rely on Remix loaders. How do they cache graphql queries? Given that they all use the same URL?
[ ] Setup a GraphQL Resource route,basic
[ ] Demo a query using directly a schema
[ ] Setup type generation
[ ] Setup Vulcan Artemis in the GraphQL Resource route
[ ] Connect to Prisma via a Vulcan connector?
Storybook
[ ] Setup Storybook
[ ] Setup storybook loading in unit tests
Testing
[ ] Verify that fixtures can be shared between Cypress, unit tests, and storybook
🇪🇺 🐸 🛵
Yarn 3 workspaces
npm install remixbeforeremix setup." on postinstall => this is probably normal at this point, since we have the same issue in raw Indie stack.remix.initfolder packages are not installed automatically either, so we need first a "cd remix.init && npm installand thenyarn run remix init`. This init script is for instance in charge of copying ".env.example" to ".env"./node_modules/.bin/run-p dev:*does work though. Same for "yarn run build". => concurrently actually have the same features and should work better, to be tested https://www.npmjs.com/package/concurrently => Remix might also update to other better maintained toolsMongo and db
GraphQL
Storybook
Testing
Vercel
Styling