hdresearch/create

Template repository for framework.

create's Issues

npm run start hits an error

This only matters for prod deploys, and it likely is just a mismatch between the dist's entry point and where we've specified it to be. Just gotta build, look, and correct.

Proper location of schema import

Right now we use a type that isn't quite correct and produces an error in server.ts. I need to drill down again and place it.

front-end needs to hit port 80 in prod, not 3040

Just a quick fix to test out soon...

Add continuous integration tests

We had a complete breakage for three days, which is of course not ideal, as a consequence of #4 / hdresearch/nolita#44. We need to have a way to assess if the template still functions; sometimes the shape of our type shifts and the props no longer drill, making exposing the events break, too. Likely what we need is to just run the fetch command against our back-end, using our custom schema, directly, and assess the shape of the core flow.

Part 1 of this is #9.

remove @ts-expect-error comments

Our types changed sometime between 1.0.0 and 1.2.0 and they have strange asymmetries now that cause errors when we look for complete vs. failed objective cases in the object. Just need to rewrite some of the unions here to be more clever to prevent oracle errors.