History log of /expo/packages/@expo/cli/src/start/server/middleware/resolveAssets.ts (Results 1 – 5 of 5)
Revision Date Author Comments
# edeec536 06-Sep-2023 Evan Bacon <[email protected]>

chore(cli): delete @expo/dev-server (#24272)

# Why

- I tried this before but the logs endpoint was blocking it.
- I forked the dev server when I wrote the original `expo/cli`, been
meaning to d

chore(cli): delete @expo/dev-server (#24272)

# Why

- I tried this before but the logs endpoint was blocking it.
- I forked the dev server when I wrote the original `expo/cli`, been
meaning to delete the original for a while. The duplicate code and
indirection is making the new server features harder to implement.

<!--
Please describe the motivation for this PR, and link to relevant GitHub
issues, forums posts, or feature requests.
-->

# How

- Copy/paste remaining code from `@expo/dev-server` in to `@expo/cli`.
- Delete `@expo/dev-server`.
- Drop unused `/logs` and json parser middleware.
- Drop logging mocks.
- Drop experimental Webpack native support.
- Drop legacy react-native middleware support (no longer needed since
everything is versioned).

<!--
How did you build this feature or fix this bug and why?
-->

# Test Plan

- Tests should keep passing.
- Need to do some actual runs since there aren't any e2e tests for
various parts of dev-server.

<!--
Please describe how you tested this change and how a reviewer could
reproduce your test, especially if this PR does not include automated
tests! If possible, please also provide terminal output and/or
screenshots demonstrating your test/reproduction.
-->

# Checklist

<!--
Please check the appropriate items below if they apply to your diff.
This is required for changes to Expo modules.
-->

- [ ] Documentation is up to date to reflect these changes (eg:
https://docs.expo.dev and README.md).
- [ ] Conforms with the [Documentation Writing Style
Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md)
- [ ] This diff will work correctly for `npx expo prebuild` & EAS Build
(eg: updated a module plugin).

---------

Co-authored-by: Expo Bot <[email protected]>

show more ...


# dc51e206 27-Apr-2022 Evan Bacon <[email protected]>

feat(cli): add `export` command (#17034)

* feat(cli): add export command

* Update CHANGELOG.md

* update tests

* Update packages/@expo/cli/CHANGELOG.md

Co-authored-by: Expo Bot <34669131+

feat(cli): add `export` command (#17034)

* feat(cli): add export command

* Update CHANGELOG.md

* update tests

* Update packages/@expo/cli/CHANGELOG.md

Co-authored-by: Expo Bot <[email protected]>

* reduce interface

* refactor

refactor

refactor

* refactor

* remove all merging code

* drop aliases

* Added asset saving tests

* refactor export code up

* Update env.ts

* Drop unused

* added e2e tests

* Dropped --quiet flag

* PR Feedback

* fix tests

* fix export tests

* Update export-test.ts

Co-authored-by: Expo Bot <[email protected]>

show more ...


# 29975bfd 28-Mar-2022 Evan Bacon <[email protected]>

fix(cli): fix type errors (#16724)

* fix(cli): fix type errors

* Update CHANGELOG.md

* Update packages/@expo/cli/CHANGELOG.md

Co-authored-by: Expo Bot <[email protected]

fix(cli): fix type errors (#16724)

* fix(cli): fix type errors

* Update CHANGELOG.md

* Update packages/@expo/cli/CHANGELOG.md

Co-authored-by: Expo Bot <[email protected]>

* fix typecheck

* Update yarn.lock

* Update package.json

* Update MetroTerminalReporter.ts

Co-authored-by: Expo Bot <[email protected]>

show more ...


# 98ecfc87 24-Mar-2022 James Ide <[email protected]>

[lint] Add "caughtErrors: 'all'" to linter config (#16591)

Why
---
ES2019 added "optional catch bindings" so that `e`/`error`/etc. don't need to be specified in catch clauses if the thrown value i

[lint] Add "caughtErrors: 'all'" to linter config (#16591)

Why
---
ES2019 added "optional catch bindings" so that `e`/`error`/etc. don't need to be specified in catch clauses if the thrown value isn't used. This changes our lint rules to warn if unnecessary error variables are declared. https://2ality.com/2017/08/optional-catch-binding.html.

In JS, as opposed to TS, we allow unused catch bindings if the variable names are prefixed with an underscore. This is so that JS targeting older JS interpreters can write `catch (_) {}` if needed. With TS we disallow unused catch bindings since tsc can compile code to its target JS version.

How
---
Added `caughtErrors: 'all'` to the no-unused-vars rule's configuration. As part of this change, I made the TypeScript linting rules apply only to .ts/.tsx/.ts.d files and updated the unit test snapshots.

Test Plan
---
Added unit tests to the linter. Ran linter over all modules in this repo with expotools.

show more ...


# 8d307f52 23-Mar-2022 Evan Bacon <[email protected]>

chore: refactor `expo/cli` to `@expo/cli` package (#16717)

* chore: refactor `expo/cli` to `@expo/cli` package

* Update CODEOWNERS

* fix linking

* fix lint script

* fix build file

* f

chore: refactor `expo/cli` to `@expo/cli` package (#16717)

* chore: refactor `expo/cli` to `@expo/cli` package

* Update CODEOWNERS

* fix linking

* fix lint script

* fix build file

* fix e2e tests

* lint before build

* use mock version

show more ...