<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in VscodeDebuggerScriptParsed.ts</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>8a424beb - [lint] Upgrade to Prettier v3, typescript-eslint to v6 (#23544)</title>
        <link>http://172.16.0.5:8080/history/expo/packages/@expo/cli/src/start/server/metro/inspector-proxy/handlers/VscodeDebuggerScriptParsed.ts#8a424beb</link>
        <description>[lint] Upgrade to Prettier v3, typescript-eslint to v6 (#23544)Why---Prettier 3 is out. Add support for it with this linter config.**Note for reviewer:** the first commit is the one with the actualchanges. The rest of this PR are changes to get the linter passing(mostly autofix).How---Update eslint-config-prettier and eslint-plugin-prettier. To addressdeprecation warnings, also update typescript-eslint/parser andtypescript-eslint/eslint-plugin.Because of an update to typescript-eslint/parser, we need to suppressdeprecation warnings (documented in a comment).Regenerated test snapshots. Due to the upgraded dependencies, typecastsand optional chaining are now auto-fixable by lint. This convertswarnings into autofixes.Test Plan---`yarn test` in the linter config. Run `expotools check --all --fix-lint--no-build --no-test --no-uniformity-check` to try this config on thewhole repo.---------Co-authored-by: Expo Bot &lt;34669131+expo-bot@users.noreply.github.com&gt;

            List of files:
            /expo/packages/@expo/cli/src/start/server/metro/inspector-proxy/handlers/VscodeDebuggerScriptParsed.ts</description>
        <pubDate>Fri, 11 Aug 2023 07:31:41 +0000</pubDate>
        <dc:creator>James Ide &lt;ide@users.noreply.github.com&gt;</dc:creator>
    </item>
<item>
        <title>033ea1fc - refactor(cli): disable inspector proxy inline source maps for vscode only (#23258)</title>
        <link>http://172.16.0.5:8080/history/expo/packages/@expo/cli/src/start/server/metro/inspector-proxy/handlers/VscodeDebuggerScriptParsed.ts#033ea1fc</link>
        <description>refactor(cli): disable inspector proxy inline source maps for vscode only (#23258)# WhyWith SDK 49, I noticed a multi-second delay in breakpoints gettingbound. This is likely due to [Metro inlining sourcemaps as base64strings](https://github.com/facebook/metro/commit/6690b393cc1812af02f8eb20853504f0a6188a83)for tools like the chrome debugger. In practice, it generates a hugebase64 string that causes this delay when decoding in vscode.# How- Added `debuggerType` to connect to the inspector proxy as a certaindebugger type (e.g. `vscode` or `generic` &lt;- default)- Added override for `Debugger.scriptParsed` to disable inlinesourcemaps for vscode only.# Test Plan~~TBD, since this also requires an update in vscode-expo (add the`type=vscode` as query param when connecting to the inspector proxy).~~This is now included in `vscode-expo-tools@1.0.6`# Checklist&lt;!--Please check the appropriate items below if they apply to your diff.This is required for changes to Expo modules.--&gt;- [ ] 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` &amp; EAS Build(eg: updated a module plugin).---------Co-authored-by: Expo Bot &lt;34669131+expo-bot@users.noreply.github.com&gt;

            List of files:
            /expo/packages/@expo/cli/src/start/server/metro/inspector-proxy/handlers/VscodeDebuggerScriptParsed.ts</description>
        <pubDate>Tue, 04 Jul 2023 08:01:18 +0000</pubDate>
        <dc:creator>Cedric van Putten &lt;me@bycedric.com&gt;</dc:creator>
    </item>
</channel>
</rss>
