Package Exports

@expo/metro-config
@expo/metro-config/babel-transformer
@expo/metro-config/babel-transformer/index.js
@expo/metro-config/build/ExpoMetroConfig.js
@expo/metro-config/build/serializer/withExpoSerializers
@expo/metro-config/build/serializer/withExpoSerializers.js
@expo/metro-config/build/transform-worker/getAssets
@expo/metro-config/build/transform-worker/getAssets.js
@expo/metro-config/package.json

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@expo/metro-config) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

`@expo/metro-config`

This package contains the default Metro config that is required for bundling apps with Expo CLI. Refer to the Expo metro.config.js docs to learn more.

metro.config.js

// Learn more https://docs.expo.io/guides/customizing-metro
const { getDefaultConfig } = require('expo/metro-config');

/** @type {import('expo/metro-config').MetroConfig} */
const config = getDefaultConfig(__dirname);

module.exports = config;

Exotic

As of SDK 51, the exotic transformer has been fully removed in favor of the default @expo/metro-config transformer. The export @expo/metro-config/transformer no longer exists.

Most of the Exotic mode performance benefits have been integrated in the default Expo CLI bundling pipeline (e.g. less AST cloning, faster worker creation), and as such, the feature no longer needs to be enabled/disabled. Setting mode: "exotic" will no longer have any additional effects over the default.

Ensure you extend the @expo/metro-config/babel-transformer when customizing babel. Learn more: Extending the Babel transformer.