* Typescript migration

* Release notes

* Update error boundary

* Breakup sidebar components

* Account and Sidebar props

* Remove button in Item component + exports cleanup

* Put accountNameStyle to Account

* Revert component ports (separated to another PR)

* Export cleanup

* Remove ErrorBoundary (separated to another PR)

* Sidebar budgetName as ReactNode

Part 4 of the migration. Final moves.

Previous PR: https://github.com/actualbudget/actual/pull/1420

Part 3 of the migration.

Part 2 here: https://github.com/actualbudget/actual/pull/1419

Part 2 of the path migration. No functional changes.

Part 1: https://github.com/actualbudget/actual/pull/1418



---------

Co-authored-by: Jed Fox <git@jedfox.com>

Moving the code to separate files. Functionally should be no
differences.

This cleans up all of the usage of `<a>` in the codebase. Now all
external links get the appropriate attributes added.

Depends on https://github.com/actualbudget/docs/pull/202.

Extracted from #984

Introduces a **ResponsiveProvider** as the sole location that tracks
window size and makes that info available to the entire app. This can be
used for media queries and size-based component switching.
---------

Co-authored-by: Jed Fox <git@jedfox.com>

<!-- Thank you for submitting a pull request! Make sure to follow the
instructions to write release notes for your PR — it should only take a
minute or two:
https://github.com/actualbudget/docs#writing-good-release-notes -->

Resolves issue #844 .

---------

Co-authored-by: biohzrddd <>

Removing `react-select` and the new autocomplete. This experiment has
failed, so cleaning things up now.

Seems to build fine, will test later.

This PR improves the consistency of the settings UI by moving everything
(except the budget name field on mobile) into `<Setting>` boxes.
Additionally, it adds a “Settings” option to the file dropdown menu (I
keep expecting it to be there, and I think it’s reasonable to expose it
in both locations so it’s easier to access)

Refactored all feature flags to use the new `useFeatureFlag` hook.

Also added a new functionality to this feature flag: ability to define
custom "default" value for a feature flag. This will allow us to enable
the new autocomplete component for everyone using Netlify builds
eventually (need to address some issues before doing so).

- Add a “hide decimal places” setting to visually hide the `.xx` from
currency values globally
- When hiding the fractional digits, slightly decrease character spacing
to allow more digits to show up

Ref: #327

New settings:
<img width="566" alt="Screenshot_2023-03-17 14 19 46"
src="https://user-images.githubusercontent.com/25517624/225986815-b884b93d-02f9-48b3-a73d-d27f90b678cf.png">


Before/after:
<img width="149" alt="Screenshot_2023-02-27 21 47 07"
src="https://user-images.githubusercontent.com/25517624/222916856-21ab4f03-56c6-4b24-8fc1-ac4b883138b7.png"><img
width="131" alt="Screenshot_2023-02-27 22 02 01"
src="https://user-images.githubusercontent.com/25517624/222916859-cf882ca3-6087-4994-818e-239c3374e412.png">

This implements a simple indicator showing the user if the currently
used version is outdated by utilising GitHub tags to track the latest
version.
Closes #463

---------

Co-authored-by: Jed Fox <git@jedfox.com>

* Allow the server to auto-configure the server URL for the client

* Extract server URL/version logic out to ensure consistent updates

* ()

* Be more explicit about when the server version is re-fetched

* Use a single layer of context provider

* Move the bootstrap route to /account/needs-bootstrap

* No more `isActual`

* Refactor to call subscribe-needs-bootstrap instead of fetch()

* Dedupe calls to subscribe-needs-bootstrap

* Don’t revalidate the server when we just validated it

* simplify

* Fix setServerURL