💡 RFC: Monorepo (Turborepo) MVP

[isaiahdahl]

Design INSPO:
https://www.figma.com/file/2X5dJO3LWpOXrF2YfsAVMQ/ChordChartJS?node-id=0%3A1

TODO:

• scaffold monorepo with a new fork of chordsheetjs as a submodule
• simple CI with test, lint across the packages
• simple stencil components using codemirror to do some simple chordpro parsing
• end to end test that by publishing them to NPM and using them in a fresh react/angular app.

[isaiahdahl]

@martijnversluis Ok so I got us to a scaffold point. I started from this example repo so that we had some examples to work from for the shared tsconfig etc. It also had ChangeSets and storybook which could be useful tools for us.

After you clone this repo run git submodule update --init --recursive to setup the submodule. Then for some reason it's not recognizing the turborepo branch so I had to cd into the chordchartjs package and change the branch to turborepo eventually it'd just be master though.

I decided to create a new repo for the new "studio" repo instead of unforking the old one. Which I renamed back to ChordSheetJS. I'm not sure if the studio name will stick for this repo or not but the idea that this repo could evolve to hold more than just the chord chart editor. (ie. PDF viewer, multitrack viewer)

So far the roadblocks I've run into are I had to create a turborepo branch on the submodule because it couldn't figure out how to find the plugin for ./node_modules/ts-pegjs in the build:pegjs command. In the turborepo branch I changed it to ../../node_modules/ts-pegjs and could get it to build. But that's not a sustainable solution.

I also had to bump some parcel package versions.

I created a stencil app trying to get some basic parsing happening but it looks like the parcel build isn't working properly. If you run yarn dev and go to localhost:3333 which is the stencil components you'll see this.

I also get the same thing when I try and run plain ol chordsheetjs

Hopefully this is a good start. Let me know what you find!