* chore: handle built css assets
* chore: let prettier handle css code
* refactor: let webpack build css assets
* chore: prettier on bskyembed
* chore: touch empty.txt on css directory
* chore: do the same to the workflow
* Install babel-plugin-react-compiler
* Install eslint-plugin-react-compiler
* Add and configure react-compiler-runtime
React Compiler uses a small cache function from React 19 at runtime.
Until it's possible to use R19 on RN, this adds a userspace
implementation to polyfill the cache function
* Add eslint-plugin-react-compiler to config
* @lingui/macro should run as the first plugin
@lingui recommends running their `macro` plugin [first in the
pipeline](https://lingui.dev/ref/macro). Normally with the React
Compiler, the compiler plugin should run first as we want to see the
original code as it was written. However, this sometimes causes
conflicts with other babel plugins.
In this case, it looks like the @lingui/macro plugin does some very
light transformation that the compiler can still understand and compile
correctly, so let's run it first.
Before this commit, the compiler would cause the @lingui/macro plugin to
crash because it seems like it would strip off the `extra.raw` property
off of StringLiterals which was being used
[here](https://github.com/lingui/js-lingui/blob/1293412c5dcc565636403443788a5b5d4ca206c1/packages/macro/src/macroJsx.ts#L395).
I need to figure out why the compiler is doing that but for now this
works and should be a safe change unless there were specific reasons
the macro plugin was placed 2nd to last.
* bskyweb: Makefile and dev env
This matches the setup for local dev testing in atproto and indigo
repos.
* gitignore: don't ignore self and .github/
* CI: golang build+test and lint actions
* bskyweb: better use of godotenv
A recent change from indigo.
* prettier: ignore top-level app.json
* CI: bump from golang 1.19 to 1.20
* bskyweb: update to golang 1.20
Eric Bailey