Skip to content

Releases: callstack/repack

4.0.0

09 May 13:44
Compare
Choose a tag to compare

Important updates

Re.Pack 4.0.0 is here 🎉

Check out Migration Guide in our fresh new docs at https://re-pack.dev

This release also marks the beginning of unified versioning for all Re.Pack packages

Special thanks to everyone involved in this release! 🙏
@thymikee @RafikiTiki @szymonrybczak @teneeto @troZee @kerm1it @krozniata @hosseinmd @lukemorawski

Major Changes

  • #430 0d96b11 Thanks @jbroma! - Upgrade to Node 18, drop support for Node 16

  • #530 470a7c1 Thanks @jbroma! - Remove ReactRefreshPlugin in favor of DevelopmentPlugin

  • #435 63d973f Thanks @jbroma! - CodeSigningPlugin no longer accepts outputPath property as configuration option, performs the code-signing in-place and integrates nicely with OutputPlugin

  • #537 6fa32cb Thanks @jbroma! - Override the default start and bundle CLI commands for enhanced functionality and compatibility with react-native versions >= 0.74. Additionally, this update ensures that running react-native run-ios or react-native run-android will launch the Re.Pack dev server by default instead of the Metro dev server.

  • #525 a74930b Thanks @jbroma! - getResolveOptions is now way more compatible with metro-resolver and @react-native/metro-config

    1. getResolveOptions now accepts a second optional parameter called options with the following properties:
      • enablePackageExports - defaults to false
      • preferNativePlatform - defaults to true
    2. Order of extensions was changed to match the order from @react-native/metro-config.
    3. Resolution via Package Exports (exports field in package.json) is now optional and disabled by default.
      It can now be enabled via getResolveOptions options parameter. This change was introduced to match metro defaults.
    4. Default conditionNames are now: ['require', 'import', 'react-native'] and match @react-native/metro-config defaults.
  • #495 50a7257 Thanks @troZee! - Add support for New Architecture

  • #508 fec8962 Thanks @RafikiTiki! - Fixed deprecated remote debugger integration:

    • Removed vendored code and used middlewares from @react-native-community/cli-server-api
    • Removed package/debugger-app and replaced it with @react-native-community/cli-debugger-ui
    • Removed vendored code responsible for integration with Flipper debugger & custom implementation of the Hermes Inspector Proxy
    • Added integration with @react-native/dev-middleware which enables us to use both Flipper and new experimental debugger

Minor Changes

  • #539 8270cb7 Thanks @jbroma! - OutputPlugin now supports configuration with empty object as compilation entry

  • #582 24585c0 Thanks @jbroma! - Use localhost as a defined default for the dev-server

  • #508 fec8962 Thanks @RafikiTiki! - Added pass-through experimentalDebugger flag to CLI commands to ensure compatibility with Metro and new experimental debugger for React Native

Patch Changes

4.0.0-rc.2

24 Apr 14:12
Compare
Choose a tag to compare
4.0.0-rc.2 Pre-release
Pre-release

Minor Changes

Patch Changes

4.0.0-rc.1

17 Apr 14:34
Compare
Choose a tag to compare
4.0.0-rc.1 Pre-release
Pre-release

Important Updates

You can now use @callstack/repack-init to use pre-releases like this one:

npx @callstack/repack-init@rc --custom-version 4.0.0-rc.1

Minor Changes

Patch Changes

4.0.0-rc.0

05 Apr 16:17
Compare
Choose a tag to compare
4.0.0-rc.0 Pre-release
Pre-release

Important Updates

  • We are deprecating @callstack/repack-debugger-app in this version and plan to remove it entirely in the next major release. We are currently working on supporting the new debugger.
  • Unified Package Versioning: This release marks the beginning of unified versioning for all Re.Pack packages

Major Changes

  • #430 0d96b11 Thanks @jbroma! - BREAKING CHANGE:

    Upgrade to Node 18, drop support for Node 16.

  • #530 470a7c1 Thanks @jbroma! - BREAKING CHANGE:

    ReactRefreshPlugin was removed.

    If you were using ReactRefreshPlugin, please switch to DevelopmentPlugin moving forward.
    Users of RepackPlugin can continue as is, with no changes required.

  • #435 63d973f Thanks @jbroma! - BREAKING CHANGE:

    CodeSigningPlugin no longer accepts outputPath property as configuration option. Instead, it performs the code-signing in-place and integrates nicely with OutputPlugin.

  • #537 6fa32cb Thanks @jbroma! - BREAKING CHANGE:

    Re.Pack commands now override the default start and bundle CLI commands for enhanced functionality and compatibility with react-native versions >= 0.74. For earlier versions of react-native (< 0.74), the traditional commands webpack-start and webpack-bundle remain available and recommended.

    This change primarily impacts setups where both Metro and Re.Pack are used simultaneously.

    To maintain your current workflow without adopting these overrides, especially to avoid conflicts in projects using both Metro and Re.Pack, you can opt out by filtering out the new command names and reverting to the legacy webpack prefixed commands:

    // react-native.config.js
    const commands = require('@callstack/repack/commands');
    
    module.exports = {
      commands: commands.filter((command) => command.name.startsWith('webpack')),
    };

    Additionally, this update ensures that running react-native run-ios or react-native run-android will launch the Re.Pack dev server by default instead of the Metro dev server.

  • #525 a74930b Thanks @jbroma! - BREAKING CHANGE:

    getResolveOptions is now way more compatible with metro-resolver and @react-native/metro-config

    1. getResolveOptions now accepts a second optional parameter called options with the following properties:
      • enablePackageExports - defaults to false
      • preferNativePlatform - defaults to true
    2. Order of extensions was changed to match the order from @react-native/metro-config.
    3. Resolution via Package Exports (exports field in package.json) is now optional and disabled by default.
      It can now be enabled via getResolveOptions options parameter. This change was introduced to match metro defaults.
    4. Default conditionNames are now: ['require', 'import', 'react-native'] and match @react-native/metro-config defaults.
  • #495 50a7257 Thanks @troZee and @teneeto for prior work! - Support for New Architecture

Minor Changes

  • #539 8270cb7 Thanks @jbroma! - OutputPlugin now supports configuration with empty object as compilation entry.

Patch Changes

3.7.0

18 Dec 15:23
Compare
Choose a tag to compare

3.7.0

Summary

This release has two main changes:

  • compatibility with the latest React Native release (0.73.x)
  • improvement in terms of webpack builds caching

Minor Changes

Patch Changes

repack-dev-server 1.1.0

18 Dec 15:18
Compare
Choose a tag to compare

1.1.0

Minor Changes

  • #475 cc997a2 Thanks @szymonrybczak! - Added X-React-Native-Project-Root header, so the RN CLI picks up the running bundler correctly

3.6.0

06 Nov 09:43
Compare
Choose a tag to compare

3.6.0

📖 Learn more about what Lazy Compilation is and how to use it:
https://re-pack.netlify.app/docs/configuration/guides/lazy-compilation

Minor Changes

3.5.1

11 Oct 15:31
Compare
Choose a tag to compare

3.5.1

Patch Changes

  • #444 88dc11f Thanks @jbroma! - Fix ValidationError in ModuleFederationPlugin caused by reactNativeDeepImports prop

3.5.0

10 Oct 16:21
Compare
Choose a tag to compare

3.5.0

Minor Changes

  • #421 7deea25 Thanks @jbroma! - Add builtin support for react-native deep imports when using Module Federation

Patch Changes

repack-init 1.1.0

10 Oct 16:19
Compare
Choose a tag to compare

1.1.0

Minor Changes