* Test a fix for electron builds

* Add release note

* add flatpack to electron build

* note

* add to workflow

* try to fix workflow

* typos

* workflow

* work

* update

* add repo

* update other electron workflow

* stable doesn't work

* fix version

* add step

* note

* fix

* add flatpack to electron build

* note

* add to workflow

* try to fix workflow

* typos

* workflow

* work

* update

* add repo

* update other electron workflow

* stable doesn't work

* fix version

* rename

* note

*  updated github issue template to hopefully reduce the amount of support

* Release notes

* Create wip.yml

Adding WIP to new PRs

* Create 2443.md

notes

* Update .github/workflows/wip.yml

Co-authored-by: Matiss Janis Aboltins <matiss@mja.lv>

* Update .github/workflows/wip.yml

Co-authored-by: Matiss Janis Aboltins <matiss@mja.lv>

* Update upcoming-release-notes/2443.md

Co-authored-by: Matiss Janis Aboltins <matiss@mja.lv>

* Update wip.yml

* Update 2443.md

* Update wip.yml

---------

Co-authored-by: Matiss Janis Aboltins <matiss@mja.lv>

* Update vite / swc / ts versions

* Release notes

* Revert root tsconfig module changes

* yarn dedupe

* Dummy update to run pipeline

* Update webpack and playwright

* Update playwright docker images

* Change the vite chunk filename hash usage

- Change to more closely match the . syntax we use with webpack
- This should fix some issues with our size compare as well
* Account for chunks being base64

* Proof of concept for switching desktop-client to vite

* Fix other packages ts tests issues

* Update jsx tests to use vitest instead of jest

* Inject our global shims properly

* Add comment regarding new plugin

* Cleanup unnessary change after rebase

* Fix inter fonts pathing

* Remove manual chunks sizes for now

Just set the limit higher

* Bring back size compare

* Suppress victory warnings

* Remove craco config now that it's not used

* Add vite basic ssl plugin

- This autogenerates self-signed certs in dev mode when HTTPS env is set
- Made to match the CRA behaviour

* Add release note

* Remove warning suppression for victory

- Updated to a rollup version that includes the fix

This reverts commit e11b6571.

Closes #1328

Closes #1471

Includes a few typographical improvements I PR’d.

(since the workflow is a `pull_request_target` one, the changes won’t
show up in the comments till this PR is merged)

The change isn’t so new anymore so I’ve updated the comment to recognize
that.

Cancel previous CI runs if a new push is made. Thus saving a bit of CI
resources.

This script is only used for the github e2e tests so doesn't need to be
inside /bin

This PR moves the size comparison action back to a separate workflow
which now uses the `pull_request_target` event. This event is triggered
at all the same times as the `pull_request` action, except that the
workflow file content comes from the target branch of the PR, and it is
run in the context of the repo owning the target branch. Practically,
this means that it will still have access to post a comment even if the
PR comes from a fork.

We don’t want the build actions to be run in a `pull_request_target`
workflow because they would get access to the secrets and be able to
perform arbitrary actions on the repository, even from fork PRs.

See the current version failing here:
https://github.com/actualbudget/actual/actions/runs/5395184895/jobs/9797388016?pr=1122

actual-server does not need to import the full actual-app/api package.
It can import only the CRDT stuff.. so I'm extracting it into a new
package to reduce the size of actual-server and make the link between
things more transparent.

This should fix the test failures on `master` — currently tests are
failing because the cache was created with an old version of Node.

After #1115, new Node.js versions will be able to be used for
development of the frontend. This PR changes the recommended Node.js
version to 18 (the current LTS version). I have also tested with 16 and
20 and it works.

I also took the opportunity to:

- move the build script that was at the project root to the `bin/`
folder
- update the `browserslist` to target Electron 24 (which is the version
we currently build against). This results in a slightly smaller bundle
due to no longer having to transpile optional chaining.

Good catch @Jackenmen in
https://github.com/actualbudget/actual/pull/948#issuecomment-1580501909
— I’ve also added a CI check to ensure bad migrations aren’t introduced
in the future.

I think if you have a budget that has managed to have this migration
applied successfully, you’ll need to manually patch
`getAppliedMigrations` in
`packages/loot-core/src/server/migrate/migrations.ts` and inject a query
to remove the old migration ID and insert the new one.

Web: https://github.com/actualbudget/actual/pull/1087
Server: https://github.com/actualbudget/actual-server/pull/207
Docs: https://github.com/actualbudget/docs/pull/179



---------

Co-authored-by: Jed Fox <git@jedfox.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>