@testing-library/react-native 14.0.0-rc.1 → 14.0.0-rc.2

package/matchers.d.ts

@@ -1 +1 @@
-export * from './build/matchers';
+export * from './dist/matchers';

package/matchers.js

@@ -1,2 +1,2 @@
-// makes it so people can import from '@testing-library/react-native/pure'
-module.exports = require('./build/matchers');
+// makes it so people can import from '@testing-library/react-native/matchers'
+module.exports = require('./dist/matchers');

package/package.json

@@ -1,9 +1,9 @@
 {
   "name": "@testing-library/react-native",
-  "version": "14.0.0-rc.1",
+  "version": "14.0.0-rc.2",
   "description": "Simple and complete React Native testing utilities that encourage good testing practices.",
-  "main": "build/index.js",
-  "types": "build/index.d.ts",
+  "main": "dist/index.js",
+  "types": "dist/index.d.ts",
   "repository": {
     "type": "git",
     "url": "https://www.github.com/callstack/react-native-testing-library.git"
@@ -23,7 +23,7 @@
     "integration"
   ],
   "scripts": {
-    "clean": "del build",
+    "clean": "del dist",
     "test": "jest",
     "test:ci": "jest --maxWorkers=2",
     "test:ci:coverage": "jest --maxWorkers=2 --collectCoverage=true",
@@ -39,7 +39,7 @@
     "validate:examples": "yarn --cwd examples/basic validate && yarn --cwd examples/cookbook validate",
     "validate:all": "yarn validate && yarn validate:examples && yarn docs:check && yarn --cwd website validate && yarn --cwd experiments-app validate",
     "validate:fix": "yarn prettier:fix && yarn lint --fix && yarn typecheck && yarn test -u && docs:generate",
-    "build:js": "babel src --out-dir build --extensions \".js,.ts,.jsx,.tsx\" --source-maps --ignore \"**/__tests__/**\"",
+    "build:js": "babel src --out-dir dist --extensions \".js,.ts,.jsx,.tsx\" --source-maps --ignore \"**/__tests__/**\"",
     "build:ts": "tsc --build tsconfig.release.json",
     "build": "yarn clean && yarn build:js && yarn build:ts",
     "release": "release-it",
@@ -47,7 +47,7 @@
     "release:codemods": "yarn test:codemods && yarn dlx codemod@latest publish codemods/v14-async-functions && yarn dlx codemod@latest publish codemods/v14-update-deps"
   },
   "files": [
-    "build/",
+    "dist/",
     "matchers.js",
     "matchers.d.ts",
     "pure.js",

package/pure.d.ts

@@ -1 +1 @@
-export * from './build/pure';
+export * from './dist/pure';

package/pure.js

@@ -1,2 +1,2 @@
 // makes it so people can import from '@testing-library/react-native/pure'
-module.exports = require('./build/pure');
+module.exports = require('./dist/pure');

package/docs/agents/architecture.md

@@ -1,21 +0,0 @@
-# Architecture And API Design
-
-## Project overview
-
-`@testing-library/react-native` provides utilities for testing React Native components in ways that resemble real usage and avoid implementation details.
-
-- Tech stack: TypeScript, React Native, Jest
-- Core principle: the closer tests are to real usage, the more confidence they provide
-- Runtime model: the library simulates the React Native runtime on top of `test-renderer`
-
-## API design principles
-
-- Prefer a small public API surface.
-- Expose underlying React and `react-reconciler` capabilities when Testing Libraries need them.
-- Render host elements only.
-- Provide escape hatches to fibers when needed.
-
-## Key entry points
-
-- `src/pure.ts`: side-effect-free core logic without auto-cleanup
-- `src/index.ts`: main entry point that re-exports `pure` and adds auto-cleanup side effects

package/docs/agents/build-and-validation.md

@@ -1,27 +0,0 @@
-# Build, Validation, And Repo Layout
-
-## Common commands
-
-- Install dependencies: `yarn install`
-- Run tests: `yarn test`
-- Run tests in CI mode: `yarn test:ci`
-- Type check: `yarn typecheck`
-- Lint source files: `yarn lint`
-- Check formatting: `yarn prettier`
-- Validate the main package: `yarn validate`
-- Build the package: `yarn build`
-
-## Command notes
-
-- `yarn lint` runs ESLint on `src`.
-- `yarn validate` runs typecheck, tests, lint, and Prettier checks for the main package.
-- `yarn build` cleans `build/`, transpiles source with Babel, and emits TypeScript declarations.
-
-## Repo layout
-
-- `src/`: source code
-- `src/pure.ts`: core logic without side effects
-- `src/index.ts`: main entry point with auto-cleanup side effects
-- `examples/`: example React Native apps
-- `website/`: documentation site
-- `codemods/`: codemod implementations and tests

package/docs/agents/code-style.md

@@ -1,12 +0,0 @@
-# TypeScript And Code Style
-
-## Linting and formatting
-
-- ESLint uses `@callstack/eslint-config` together with `typescript-eslint`.
-- Important enforced rules include `no-console` and consistent type imports.
-- Prettier is the formatter.
-- Formatting defaults include single quotes and trailing commas.
-
-## Imports
-
-- Keep imports sorted with `eslint-plugin-simple-import-sort`.

package/docs/agents/example-apps.md

@@ -1,56 +0,0 @@
-# Example App Regeneration
-
-## General workflow
-
-- Regenerate Expo example apps in a temporary directory, then copy the fresh scaffold into place.
-- Before replacing an example app, move the current app directory to `/tmp` so repo-specific files can be restored selectively.
-- After copying a generated app into `examples/`, remove the generated `.git` directory and `node_modules`, then reinstall from inside the repo workspace.
-
-## `examples/basic`
-
-- Generate from the Expo blank TypeScript template:
-  - `yarn create expo-app /tmp/rntl-basic-fresh --template blank-typescript --yes`
-- Restore these repo-specific files on top of the fresh scaffold:
-  - `App.tsx`
-  - `components/`
-  - `__tests__/`
-  - `theme.ts`
-  - `jest.config.js`
-  - `jest-setup.ts`
-  - `babel.config.js`
-  - `eslint.config.mjs`
-  - `README.md`
-  - `.expo-shared/assets.json` if it existed before
-- Keep the fresh Expo entrypoint `index.ts`.
-- Update `package.json` and `app.json` to match repo naming and scripts.
-
-## `examples/cookbook`
-
-- Generate from a router-enabled Expo scaffold:
-  - `yarn create expo-app /tmp/rntl-cookbook-fresh --example with-router --yes`
-- Restore these repo-specific files on top of the fresh scaffold:
-  - `app/`
-  - tutorial test directories such as `basics-tutorial/` and `basics-tutorial-react-strict-dom/`
-  - `theme.ts`
-  - `jest.config.js`
-  - `jest-setup.ts`
-  - `babel.config.js`
-  - `.eslintrc`
-  - `.eslintignore`
-  - `README.md`
-  - custom assets not present in the scaffold, such as `assets/gradientRNBanner.png`
-  - `.expo-shared/assets.json` if it existed before
-- Keep the fresh Expo Router entry setup.
-- Reapply the cookbook-specific dependency set in `package.json` and `app.json`.
-
-## Validation after regeneration
-
-- Run these commands from inside the regenerated app directory:
-  - `yarn expo install --check`
-  - `yarn lint`
-  - `yarn typecheck`
-  - `yarn test --watchman=false`
-
-## Lockfile guidance
-
-- If the fresh scaffold causes dependency-resolution churn, restore the previous `yarn.lock` first and then run `yarn install` instead of re-resolving the full tree.

package/docs/agents/git-workflow.md

@@ -1,13 +0,0 @@
-# Git, Releases, And PR Workflow
-
-## Commits and releases
-
-- Use Conventional Commits such as `fix:`, `feat:`, and `chore:`.
-- Releases are managed with `release-it`.
-
-## PR draft workflow
-
-- Maintain `PR.txt` at the repository root using the structure from `.github/pull_request_template.md`.
-- Keep `PR.txt` aligned with the current branch diff relative to `origin/main`.
-- Include tests actually run and any known validation gaps in `PR.txt`.
-- Do not commit `PR.txt`.

package/docs/agents/testing.md

@@ -1,20 +0,0 @@
-# Testing Conventions
-
-## Test stack
-
-- Test framework: Jest with the `react-native` preset
-- Test environment setup: `jest-setup.ts`
-- Auto-cleanup is configured from `src/index.ts` unless explicitly skipped
-
-## Test location and coverage
-
-- Library tests are typically colocated under `src/**/__tests__`
-- Coverage is collected from `src` and excludes test files
-
-## Test organization
-
-- Use `describe` blocks to group tests by theme.
-- Do not put all tests into a single `describe`.
-- Avoid nested `describe` blocks.
-- If a `describe` would contain only one test, make that test top-level instead.
-- Prefer `test` over `it`.