akveo/react-native-ui-kitten @ui-kitten/metro-config@6.0.0

on GitHub

Major Changes

• e6651ad Thanks @bataevvlad! - UI Kitten v6: React 19, React Native 0.81, Expo 54, all components migrated to functional, ESM build system, New Architecture ready.

Patch Changes

• #1871 2376396 Thanks @bataevvlad! - Fix @ui-kitten/metro-config being unusable from metro.config.js.

  The package is loaded by Node, not by Metro, but it was published as ESM only. services/project.service.ts used __dirname, which does not exist in ESM, so the documented usage threw ReferenceError: __dirname is not defined in ES module scope and took the whole Metro config down with it. The ui-kitten CLI binary was broken for a related reason: bin/ui-kitten required ../cli, a directory that ships only TypeScript sources.

  • Build this package as CommonJS instead of ESM, and emit real .d.ts files instead of pointing types at the raw source.
  • Resolve the project root from process.cwd() rather than from the module's own location, which was also off by two directory levels in the compiled output.
  • Point the ui-kitten binary at the compiled CLI.

• #1871 5714ed0 Thanks @bataevvlad! - Compile Eva styles when metro.config.js is loaded, not on a Metro reporter event.

  MetroConfig.create() only ran the bootstrap from its reporter.update handler when Metro
  emitted initialize_started. Tools that replace the reporter never delivered that event, so
  under Expo CLI (expo start, expo export) the cache in node_modules/.cache/ui-kitten/ was
  never written and @ui-kitten/eva/index.js never received its exports.styles line. The
  bootstrap now runs eagerly and synchronously inside create(); the reporter hook is kept for
  bare Metro and still runs it again (idempotently) on initialize_started.

  Other fixes in the same package:

  • The custom-mapping watcher is installed from create() itself (so it also works under
    Expo CLI, which never delivers Metro's initialize_started event), and only when
    customMappingPath is a non-empty string pointing at an existing file. It polls with
    persistent: false, so a dev server keeps recompiling on changes while one-shot processes
    (expo export, a script that requires metro.config.js, the CLI) still exit on their own.
    Previously an absent path resolved to the project root, so fs.watchFile('./') polled the
    whole project directory every 100 ms and kept any Node process that loaded the config alive.
  • A missing or non-JSON custom mapping is reported as a warn naming the path that was tried,
    instead of crashing with TypeError: Cannot read properties of null (reading 'length').
  • BootstrapService.run returns a boolean, and ui-kitten bootstrap sets exit code 1 on an
    unknown package, a project without Eva packages or a bad custom mapping, so CI can detect it.
  • The exports.styles line is appended without accumulating blank lines; the eva index always
    ends with exactly one newline after the append.
  • success Successfully bootstrapped … is only printed when the cache was written or the
    export line was appended. A no-op run prints nothing from the service; the CLI prints
    info <package> styles are up to date instead, so a postinstall or a bundler that
    bootstraps twice no longer repeats the success line.
  • The cache checksum now covers the eva mapping as well as the custom mapping, so the styles
    are rebuilt exactly when either file changed (including after upgrading the eva package)
    and are left alone otherwise.
  • Installed-package checks look at the file system instead of require-ing the eva package
    index. Once bootstrapped, that index requires the generated cache, so wiping
    node_modules/.cache used to make the next bootstrap report the package as not installed
    instead of regenerating the cache.

• Updated dependencies [657fc23, 03cad37, e6651ad]:

  • @ui-kitten/processor@6.0.0
  • @ui-kitten/mapping-base@6.0.0