re-pack.dev valid
Re.Pack
A modern build tool for React Native that brings the Rspack and webpack ecosystem to mobile React Native apps
- Authority
- 50 reach 0 · trust 10 · quality 25 · freshness 15
- Tier
- listed
- llms.txt
- https://re-pack.dev/llms.txt
- llms-full.txt
- https://re-pack.dev/llms-full.txt
- Sections
- 3
- Links
- 53
- Size
- 18667 bytes
- Registered
- 2023-06-21
- Country
- United States Hosting inference
- Hosting country
- United States Hosting inference
- Country evidence
- No published address evidence collected yet
- Categories
- Developer tools
- For agents
- Documentation: developer or product docs worth reading, nothing to call
- First seen
- 2026-10-24T22:47:42.655Z
- Last checked
- 2026-10-24T22:47:43.410Z
- Badge
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-24T22:47:42.749Z. Cached copy · Source on re-pack.dev
# Re.Pack
> A modern build tool for React Native that brings the Rspack and webpack ecosystem to mobile React Native apps
## Docs
- [Introduction](/docs/getting-started/introduction.md): Before diving deep into Re.Pack and introducing it into project, it's important to understand when and why to use Re.Pack and how does it compare with alternatives.
- [Quick start](/docs/getting-started/quick-start.md)
- [Microfrontends](/docs/getting-started/microfrontends.md): Microfrontends (MFEs) are an architectural approach that breaks down a web application’s frontend into smaller, independently deployable pieces that can be downloaded on demand. Think of them as the frontend equivalent of microservices: instead of one massive, tangled codebase, you get modular chunks that different teams can own, develop, and ship on their own timelines. It's important to note that we're not talking about producing a single JS bundle from multiple independent teams. It's about producing many JS bundles that can be later downloaded on demand by a mobile app. While web MFEs and microservices are often about using independent tech stacks, it's different on mobile iOS and Android ecosystems due to platform constraints and app store rules that typically prevent loading any compiled code. Re.Pack is largely designed to enable microfrontends on mobile. It's one of the key differences between other React Native bundlers, such as Metro, which don't support this architecture out of the box.
- [Module resolution](/docs/features/module-resolution.md): Module resolution is the process by which a bundler determines which file to load when you import a module. In React Native, this process has unique requirements—platform-specific files, scaled assets, and the react-native condition in package exports all need special handling. Re.Pack is designed to match Metro's resolution behavior as closely as possible, ensuring that projects migrating from Metro or using libraries designed for Metro work correctly. Getting module resolution right ensures that: Platform-specific files (.ios.js, .android.js) load correctly for each targetLibraries with React Native-specific entry points work as expectedScaled assets (@2x, @3x images) resolve properly
- [Code splitting](/docs/features/code-splitting.md): Code Splitting is a technique that splits the code into multiple files, which can be loaded on demand and in parallel. It can be used to: Optimize the initial size of the application and to improve the startup performance by deferring the parsing (only with JSC) and execution (JSC and Hermes) of the non-critical code.Dynamically deliver content and features to the users based on runtime factors: user's role, subscription plan, preferences etc.For developers and companies: split and isolate pieces of the product to improve scalability and reduce coupling. Code Splitting is one of the most important features in Re.Pack, and it's based on Webpack's infrastructure as well as the native module that allo
…Related sites
Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| reactnative.dev | React Native · Learn once, write anywhere | documentation Developer tools Open source projects +1 | DE | 67 | ✓ | ✓ | |
| rspack.rs | Rspack | documentation Developer tools Open source projects | RS | 52 | ✓ | ✓ | |
| rnfirebase.io | React Native Firebase | documentation APIs and SDKs Developer tools +1 | — | 51 | ✓ | ✓ | |
| expo.dev | Expo documentation | documentation Developer tools | — | 68 | ✓ | ✓ | |
| rsbuild.rs | Rsbuild | documentation Developer tools Documentation and reference | RS | 51 | ✓ | ✓ | |
| rslib.rs | Rslib | documentation Developer tools Documentation and reference | RS | 45 | ✓ | ✓ | |
| stalliontech.io | React Native Stallion | documentation Cybersecurity Developer tools +1 | — | 54 | ✓ | ✓ | |
| cresc.dev | Cresc | interface Developer tools APIs and SDKs | — | 50 | ✓ | ✓ |
Machine-readable: GET /v1/resolve?q=re-pack.dev · GET /v1/domain/re-pack.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage re-pack.dev, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for re-pack.dev:
1. POST https://agentwebmap.com/v1/sites/re-pack.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://re-pack.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/re-pack.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/re-pack.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.