refactor(workspaces): yarn workspaces

[elbotho]

Changelog:

• /src moved to apps/frontend/src
• all yarn commands can still be executed from project root, like yarn or yarn dev
• editors should be able to pick up correct config (prettier, eslint, tsc)
• CI and vercel now work with new folder structure

Todos:

• avoid two subdirectories with same name frontend, e.g. rename apps/frontend to apps/web
• check prisma integration - it's a bit all over the place :) at least make sure that it works - env setup is working on vercel
• move readme back to top-level?
• make prettier and eslint work with repo-wide settings
• fix bundle size hack (e.g. https://frontend-git-yarn-workspaces-serlo.vercel.app/biologie)
• update vs code settings for eslint

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
frontend	✅ Ready (Inspect)	Visit Preview		Dec 6, 2023 10:38am
frontend-monorepo	🔄 Building (Inspect)	Visit Preview	💬 Add feedback	Dec 6, 2023 10:38am

[Entkenntnis]

Thank you very much! Let's get this working 👍

[elbotho]

BTW: I just aliased all frontend commands so we can work with them as we usually do. Basically just some paths changed.
Since this is still mostly frontend and we work on is a lot more I think that makes sense.

Not yet sure about the eslint errors.
Ah and new vercel intergration sounds smart.

[Entkenntnis]

@elbotho I would suggest disabling jest. The tests are not maintained, and also quite trivial? (and probably completely outdated atm ...)

[Entkenntnis]

ups, we broke bundle size 👀

[elbotho]

@elbotho I would suggest disabling jest. The tests are not maintained, and also quite trivial? (and probably completely outdated atm ...)

I added some 2 months ago, but I'm okay with disabling the failing tests suite for now.

ups, we broke bundle size 👀

yeah, that's weird. We should make sure the check is correct first though. Not even sure why it runs in this pr.

[elbotho]

Prettier works again for me, in frontend and on repo-root both with terminal and vscode.

ESlint also works with a new VSCode setting of eslint.workingDirectories": [{ "mode": "auto" }].
It seems to be a common thing with monorepos and since it works from the terminal the project config should be correct.
I'm not sure if it actually worked before or I just did not see it, but I did not find another way.

There is still one unexpected ESLint error (only in IDE) in feature-i18n.ts at getInstanceDataByLang. Did not investigate far but that might be related to ramda.