Changes in env.ts

9a348a4e - chore(router): pull in stable changes from #23795 (#23890)

Thu, 10 Aug 2023 16:44:44 +0000

chore(router): pull in stable changes from #23795 (#23890)# Why - #23795 is blocked on some difficult issues. This PR pulls in the safe changes from that PR so they don't get lost. --------- Co-authored-by: Expo Bot <34669131+expo-bot@users.noreply.github.com> List of files: /expo/packages/@expo/cli/src/utils/env.ts

2fbedb18 - feat(cli, metro): add inverse import error stack (#23551)

Fri, 28 Jul 2023 03:48:35 +0000

feat(cli, metro): add inverse import error stack (#23551)# Why Many users encounter issues where a library reaches into react-native internals on web and the error isn't helpful. This PR creates a graph of resolutions to print the full stack of imports that lead to an invalid resolution. This helps show which application code can be modified to fix a bug. Unclear if we want to add an experimental version of this in Expo CLI or in Metro. For now, I'm opening the draft so some power-users can pull the branch and use it to debug their projects. I'll be splitting parts of this PR out and merging them into upstream (expo/expo) in the meantime. ### Before ### After ## Usage in dev - Pull this branch - [Setup local CLI in dev](https://github.com/expo/expo/blob/main/packages/%40expo/cli/README.md#contributing). - Start your project with local CLI in dev. # Test Plan - TBD --------- Co-authored-by: Expo Bot <34669131+expo-bot@users.noreply.github.com> List of files: /expo/packages/@expo/cli/src/utils/env.ts

0b7c94a9 - [cli] Use node server default port selection for SSO login server (#23505)

Thu, 13 Jul 2023 19:14:03 +0000

[cli] Use node server default port selection for SSO login server (#23505) List of files: /expo/packages/@expo/cli/src/utils/env.ts

d88ac65d - [cli] Add support for SSO user type and log in with SSO (#22945)

Tue, 11 Jul 2023 23:00:02 +0000

[cli] Add support for SSO user type and log in with SSO (#22945) List of files: /expo/packages/@expo/cli/src/utils/env.ts

e32ccf9f - feat(cli): improve offline support (#22961)

Wed, 21 Jun 2023 19:55:36 +0000

feat(cli): improve offline support (#22961)# Why Offline support is sometimes needed in parts of other commands besides `start`, this PR introduces an `EXPO_OFFLINE` env var which can be generally used to force offline support. # How - `EXPO_OFFLINE` - Show a better error message when your computer is connected to wifi but there's no signal. - Assert in `npx expo login` and `npx expo register` when `EXPO_OFFLINE` is set. - Fail better when validating versions offline. In the case of running `npx expo` without wifi: ## Before ``` june-16 �� nexpo Starting project at /Users/evanbacon/Documents/GitHub/lab/june-16 Starting Metro Bundler Unable to reach Expo servers. Falling back to using the cached dependency map (bundledNativeModules.json) from the package "expo" installed in your project. FetchError: request to https://api.expo.dev/v2/versions/latest failed, reason: getaddrinfo ENOTFOUND api.expo.dev FetchError: request to https://api.expo.dev/v2/versions/latest failed, reason: getaddrinfo ENOTFOUND api.expo.dev at ClientRequest. (/Users/evanbacon/Documents/GitHub/expo/node_modules/node-fetch/lib/index.js:1491:11) at ClientRequest.emit (node:events:513:28) at TLSSocket.socketErrorListener (node:_http_client:502:9) at TLSSocket.emit (node:events:513:28) at emitErrorNT (node:internal/streams/destroy:151:8) at emitErrorCloseNT (node:internal/streams/destroy:116:3) at process.processTicksAndRejections (node:internal/process/task_queues:82:21) ``` ## After ``` june-16 �� nexpo Starting project at /Users/evanbacon/Documents/GitHub/lab/june-16 Starting Metro Bundler Unable to reach Expo servers. Falling back to using the cached dependency map (bundledNativeModules.json) from the package "expo" installed in your project. CommandError: Network connection is unreliable. Try again with the environment variable `EXPO_OFFLINE=1` to skip network requests. ``` # Test Plan - Updated tests and added new tests for things like the register command. --------- Co-authored-by: Expo Bot <34669131+expo-bot@users.noreply.github.com> List of files: /expo/packages/@expo/cli/src/utils/env.ts

94b54ec3 - chore(cli, docs): update typed routes (#22848)

Tue, 20 Jun 2023 22:34:28 +0000

chore(cli, docs): update typed routes (#22848)# Why I keep getting DMs about this feature being confusing so I'm doing a pass to try and bring it to parity with the rest of our offering. # How - Update the experimental docs to not be a general "TypeScript" guide but rather, be focused on the "Typed Routes" feature. - Use the new `experiments.typedRoutes` flag and not an environment variable. https://github.com/expo/universe/pull/12590 - Drop flag misinfo in the Expo CLI docs "This includes support for the network inspector." - Add a slightly more e2e test for the side-effects. - Document how to actually turn the feature on. --------- Co-authored-by: Aman Mittal Co-authored-by: Expo Bot <34669131+expo-bot@users.noreply.github.com> List of files: /expo/packages/@expo/cli/src/utils/env.ts

33bd1a45 - refactor(cli): enable inspector proxy with network support by default (#22936)

Sat, 17 Jun 2023 14:52:46 +0000

refactor(cli): enable inspector proxy with network support by default (#22936)# Why Flipping this switch to be opt-out for SDK 49. # How - Renamed `EXPO_USE_CUSTOM_INSPECTOR_PROXY=true` to `EXPO_NO_INSPECTOR_PROXY=false` > This change made more sense as you would have to set `EXPO_USE_CUSTOM_INSPECTOR_PROXY=false` to revert back to the original (Metro) inspector proxy. # Test Plan - `$ EXPO_DEBUG=true expo start` -> should mention `Expo inspector proxy enabled` in the debug logs. # Checklist - [x] 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 <34669131+expo-bot@users.noreply.github.com> List of files: /expo/packages/@expo/cli/src/utils/env.ts

60d28ff6 - feat(cli): Add support for Metro lazy bundling (#22724)

Sat, 03 Jun 2023 19:41:03 +0000

feat(cli): Add support for Metro lazy bundling (#22724)# Why - Companion to https://github.com/expo/router/pull/622 # How - Add `lazy` query parameter for Metro requests and `EXPO_NO_METRO_LAZY` to disable the feature. Abiding by https://github.com/react-native-community/discussions-and-proposals/blob/main/proposals/0605-lazy-bundling.md#__loadbundleasync-in-metro # Test Plan - Works when used with https://github.com/expo/router/pull/622 --------- Co-authored-by: Expo Bot <34669131+expo-bot@users.noreply.github.com> List of files: /expo/packages/@expo/cli/src/utils/env.ts

9580591f - feat(metro-config, cli): CSS serializer (#22325)

Sun, 30 Apr 2023 20:46:17 +0000

feat(metro-config, cli): CSS serializer (#22325)# Why In order to support static CSS in development mode, we need to update the metro serializer to support returning the JS and CSS assets. We now inline the CSS in the HTML before sending to the client, this allows for testing how the website works with JS disabled. We use the same style tag id to continue to support HMR for styles during subsequent updates. This change also refactors how exports work to serialize JS and CSS at the same time (i.e. after the native transformations). # How # Test Plan # Checklist - [ ] 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 <34669131+expo-bot@users.noreply.github.com> List of files: /expo/packages/@expo/cli/src/utils/env.ts

1117330a - feat: typed route generation for expo router (#21651)

Fri, 07 Apr 2023 04:55:26 +0000

feat: typed route generation for expo router (#21651)> Draft PR - just seeking feedback on the implementation. # Why WIP implementation of route generation for Expo Router. # How ## Typescript bootstrapping This is expands the Typescript bootstrapping to also accommodate for long-lived typescript watchers. - Changes `waitForMetroToObserveTypeScriptFile` to `metroWatchTypeScriptFiles` - Processes are now responsible to disabling their watcher - tsconfig can optionally be watched ## Type generation `typedRouteGenerator` is invokes after the CLI has bootstrapped TypeScript. - Generates types only for absolute paths - Supports static and dynamic routes - Supports URL normalisation (TODO: Need unit tests for these!) - Supports dynamic route parameter typing # Test Plan `EXPO_ROUTER_TYPED_ROUTES=true nexpo start` // Todo # Checklist - [x] Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md). - [x] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md) - [x] This diff will work correctly for `expo prebuild` & EAS Build (eg: updated a module plugin). --------- Co-authored-by: Evan Bacon List of files: /expo/packages/@expo/cli/src/utils/env.ts

f479be69 - chore(cli): switch `EXPO_USE_PATH_ALIASES` to `expo.experiments.tsconfigPaths`. (#21897)

Thu, 30 Mar 2023 03:10:43 +0000

chore(cli): switch `EXPO_USE_PATH_ALIASES` to `expo.experiments.tsconfigPaths`. (#21897)# Why - It's a bit harder to set env vars and users will want this either always on or always off. - Expo Config makes it easier to deprecate values on a per-version basis. https://github.com/expo/universe/pull/11872 - Comment out references to the path aliases feature until we're closer to launch. Users are getting confused when they see the feature documented. --------- Co-authored-by: Expo Bot <34669131+expo-bot@users.noreply.github.com> List of files: /expo/packages/@expo/cli/src/utils/env.ts

0a6ddb20 - feat(cli): add basic static rendering for router projects (#21572)

Mon, 13 Mar 2023 15:57:58 +0000

feat(cli): add basic static rendering for router projects (#21572)# Why - Implement an experimental static rendering system for Metro websites using Expo Router. - Behavior is undocumented and highly experimental. # How - Add support to `start` and `export` which pre-renders static web pages to HTML to improve SEO support on web. - The system implements [React Navigation's SSR](https://reactnavigation.org/docs/server-rendering) support. - Head elements can be used with `import { Head } from 'expo-router/head'`. - The root HTML is not exposed to the user. - There are no data fetching mechanisms. - There's no ability to provide a 404 page or other server features. # Test Plan - e2e test for exporting a router project statically. - `EXPO_USE_STATIC=1 yarn expo` -> websites are pre-rendered before being served. - `EXPO_USE_STATIC=1 yarn expo export -p web` -> static routes are rendered to static HTML files by the same name (dynamic routes are not supported). # Checklist - [ ] 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 `expo prebuild` & EAS Build (eg: updated a module plugin). --------- Co-authored-by: Expo Bot <34669131+expo-bot@users.noreply.github.com> List of files: /expo/packages/@expo/cli/src/utils/env.ts

5234fe38 - feature(cli): add custom inspector proxy based on `metro-inspector-proxy` (#21449)

Wed, 08 Mar 2023 17:16:56 +0000

feature(cli): add custom inspector proxy based on `metro-inspector-proxy` (#21449)# Why Fixes ENG-7467 Related #21265 This is an initial draft to extend the CDP functionality of `metro-inspector-proxy`. # How The implementation is slightly wonky around the `ExpoInspectorDevice`. We want to reuse as much as possible from `metro-inspector-proxy`, but we need to add stateful data per device. In order to achieve that, we generate a new class type, based on the user's installed `metro-inspector-proxy`. This makes everything less readable but should include future updates in these classes. As for the `ExpoInspectorProxy`, to avoid having to do the same thing, we just wrap the whole inspector class and reuse what we can. The device map is "linked" within the original inspector proxy instance, making the data available to all methods that need it. # Test Plan Enable this feature with `EXPO_USE_CUSTOM_INSPECTOR_PROXY=1` - [x] See tests for the actual CDP events we handle. - [ ] See tests on the "bootstrapping code" to create the inspector and devices. # Checklist - [ ] 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 `expo prebuild` & EAS Build (eg: updated a module plugin). --------- Co-authored-by: Evan Bacon List of files: /expo/packages/@expo/cli/src/utils/env.ts

d8009c4b - feat(cli): add support for path aliases and absolute imports (#21262)

Fri, 24 Feb 2023 18:20:14 +0000

feat(cli): add support for path aliases and absolute imports (#21262)# Why - In Expo Router, you have to import outside of the `app` directory which does not spark joy at scale (e.g. `../../../../../../`). - This is pretty standard functionality in web development, feels odd not having it in our "Metro for web" system. # How - Add support for `compilerOptions.baseUrl` from `tsconfig.json` and `jsconfig.json` files to Metro. This enables absolute imports. - Add support for `compilerOptions.paths` aliases from `tsconfig.json` and `jsconfig.json` files to Metro. This enables path aliases. Tried to keep the implementation as close to TypeScript as possible to reduce maintenance. - Absolute imports utilize built-in Metro behavior making it more reliable. We basically just register the baseUrl as a location to search for node modules. - Couldn't decide where to document the feature so I put it in multiple places. - We might need to update expo jest to have similar functionality in the future (it might already support these fields, didn't check). # Test Plan - Added some unit tests for path aliases (non-exhaustive). - For correctness, you can use this feature in vscode and all autocomplete suggestions should work as the bundling now matches the built-in resolution. # Checklist - [ ] 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 `expo prebuild` & EAS Build (eg: updated a module plugin). --------- Co-authored-by: Expo Bot <34669131+expo-bot@users.noreply.github.com> List of files: /expo/packages/@expo/cli/src/utils/env.ts

be2ffbef - feat(cli, metro-config): implement new unstable_serverRoot feature (#21088)

Mon, 13 Feb 2023 23:33:40 +0000

feat(cli, metro-config): implement new unstable_serverRoot feature (#21088)# Why - Metro web doesn't work with monorepos because requests that look up past the project root like `/../../` will be collapsed to `/` which breaks a number of features. - Metro added `unstable_serverRoot` which we now automatically set to the workspace root when `EXPO_USE_METRO_WORKSPACE_ROOT=1` is enabled. If this works well at scale, we'll enable the feature by default. --------- Co-authored-by: Expo Bot <34669131+expo-bot@users.noreply.github.com> List of files: /expo/packages/@expo/cli/src/utils/env.ts

48783050 - fix(cli): prevent using default port 80 with tunnels (#18475)

Thu, 10 Nov 2022 04:21:17 +0000

fix(cli): prevent using default port 80 with tunnels (#18475) List of files: /expo/packages/@expo/cli/src/utils/env.ts

8c8eefe0 - feat(cli): add proxy support (#19592)

Tue, 18 Oct 2022 21:27:32 +0000

feat(cli): add proxy support (#19592)* feat: add proxy support * Update expo-cli.mdx * Update wrapFetchWithProxy.ts * Update packages/@expo/cli/CHANGELOG.md Co-authored-by: Expo Bot <34669131+expo-bot@users.noreply.github.com> * Create wrapFetchWithProxy.test.ts * Update env.ts * Update docs/pages/workflow/expo-cli.mdx Co-authored-by: Aman Mittal Co-authored-by: Expo Bot <34669131+expo-bot@users.noreply.github.com> Co-authored-by: Aman Mittal List of files: /expo/packages/@expo/cli/src/utils/env.ts

5723d92e - feat: add EXPO_TUNNEL_SUBDOMAIN to control the ngrok subdomain config (#19507)

Tue, 18 Oct 2022 17:40:45 +0000

feat: add EXPO_TUNNEL_SUBDOMAIN to control the ngrok subdomain config (#19507)* feat: add EXPO_TUNNEL_SUBDOMAIN to control the ngrok subdomain configuration * Update packages/@expo/cli/CHANGELOG.md Co-authored-by: Expo Bot <34669131+expo-bot@users.noreply.github.com> * Update AsyncNgrok-test.ts Co-authored-by: Expo Bot <34669131+expo-bot@users.noreply.github.com> List of files: /expo/packages/@expo/cli/src/utils/env.ts

ca84f1cd - feat(cli): Make Expo Metro config for web resolve projects using same `package.json` main fields as Expo Webpack (#19529)

Fri, 14 Oct 2022 19:41:52 +0000

feat(cli): Make Expo Metro config for web resolve projects using same `package.json` main fields as Expo Webpack (#19529)* fix: ensure web is setup every time * fix(cli): use correct main fields for Metro web * Update packages/@expo/cli/CHANGELOG.md Co-authored-by: Expo Bot <34669131+expo-bot@users.noreply.github.com> * Update docs/pages/workflow/expo-cli.mdx Co-authored-by: Aman Mittal * Update docs/pages/workflow/expo-cli.mdx Co-authored-by: Aman Mittal Co-authored-by: Expo Bot <34669131+expo-bot@users.noreply.github.com> Co-authored-by: Aman Mittal List of files: /expo/packages/@expo/cli/src/utils/env.ts

212e3a1a - [cli] ensure that development build is installed when opening interstitial page (#18836)

Mon, 26 Sep 2022 18:23:37 +0000

[cli] ensure that development build is installed when opening interstitial page (#18836)Co-authored-by: evanbacon List of files: /expo/packages/@expo/cli/src/utils/env.ts