# NoUnityCN: a Next.js front end over Unity's public editor download metadata

> A search and listing site for international Unity Editor versions, built as a single app/ directory that runs on either Next.js or vinext, so the same source deploys to Vercel or to Cloudflare Workers. Useful as a reference for dual-framework deployment, and not a mirror of anything, since the README states it holds no data and provides no licence files.

**DanKE123abc/NoUnityCN** — 🔥✅ Unity国际版下载站，可通过直链或者Unity Hub下载例如Unity 6等Unity Editor的国际版，支持添加组件、下载国际版Unity Hub、包含长期支持版、技术支持版、测试版、预览版的Unity。

- Repository: https://github.com/DanKE123abc/NoUnityCN
- Website: https://nounitycn.danke666.top
- Stars: 1,949 · Forks: 83
- Language: TypeScript
- License: MIT
- Published: 2026-10-16 · Updated: 2026-10-16 · Language: en
- Canonical page: https://hysenlabs.com/projects/danke123abc-nounitycn

## What the project claims to be, in its own terms

NoUnityCN presents itself as a version search service for overseas Unity developers who need a Chinese language interface, built on Unity's official public interfaces, with the explicit statement that no data is retained.

The positioning section is unusually precise, and it is worth reading before judging what the code does. The README states the project is not a cracking, modification or downloading tool, but a search service built with official public interfaces. It says the project respects copyright and will not provide pirated or cracked versions. The target audience is overseas developers working in China, or working in Chinese as a working language, or needing remote assistance, and it explicitly does not serve developers in Greater China, who are pointed to the Tuanjie engine instead.

Three further constraints appear in the notice block. The download service is provided by a separate open source project, file-proxy, with a request not to use it commercially. A caution states the download service comes from a public-benefit project and may be interrupted at any time for technical reasons. And the site states it provides no technical authorisation files such as activation licences, does not serve users outside Unity's supported regions, and that users should confirm compliance with local software regulations.

## Two frameworks, one app/ directory, and different dev ports

The deployment guide is the most reusable part of the repository, and its shape is unusual. The same app/ source is shared by two frameworks, and switching between them requires no change to business code.

The first is Next.js, using the official workflow, aimed at general Node.js platforms such as Vercel. The second is vinext, which reimplements the Next.js interface on top of Vite and targets Cloudflare Workers.

The port difference is the clearest signal that these are two separate dev servers:

```bash
# 本地开发（默认端口 3000）
pnpm dev

# 生产构建
pnpm build

# 本地预览生产构建
pnpm start
```

for Next.js, and:

```bash
# 本地开发（默认端口 3001）
pnpm dev:vinext

# 生产构建（输出到 dist/ 目录）
pnpm build:vinext

# 本地预览生产构建
pnpm start:vinext
```

for vinext. The vinext build outputs to dist/ where the Next.js build outputs to .next. That difference propagates into deployment: the Vercel preset uses Output Directory .next, while the Workers path deploys the dist/ output.

## The vinext path needs Cloudflare resources configured before it works

The Cloudflare Workers path ships with its configuration already in the repository, namely wrangler.jsonc, vite.config.ts and worker/index.ts. What it cannot ship is the account side, so the README lists four resources to create in the Cloudflare Dashboard and then synchronise into wrangler.jsonc.

A Worker must be created with a name matching the name field in wrangler.jsonc. A KV Namespace must be created and its id substituted into kv_namespaces[].id, which is used for data caching. Image Resizing must be enabled in the Worker settings if image optimisation is used. And a custom domain must be bound, the README giving a *.danke666.top example, to complete the origin configuration.

Deployment itself is one command after the build:

```bash
pnpm exec vinext deploy          # 或 pnpm exec wrangler deploy
```

If pnpm build:vinext has already run and dist/ exists, wrangler can be used directly instead. For a custom domain, the README suggests adding the configuration and running a dry run to preview the effective configuration:

```bash
pnpm exec wrangler deploy --dry-run
```

Secrets are not needed as things stand. The README states the project relies on no server side keys, and that if any are added later they are configured with pnpm exec wrangler secret put <KEY> or declared in the vars block of wrangler.jsonc.

## The Vercel path is four steps and a preset

Deployment to Vercel is described as importing the repository into Vercel with the repository root as the project root. The framework preset is detected automatically as Next.js, the build command is pnpm build, and the output directory is .next.

One detail in the Next.js section concerns the docs route. The README states that the /docs path is forwarded by rewrites in next.config.mjs to a static directory, so the public/docs assets must exist at build time. That is a build-time dependency rather than a runtime one, and it is the sort of thing that fails on a clean checkout.

The guide also points at the Vercel CLI for command line deployment, installed globally with pnpm add -g vercel and then run as pnpm vercel.

## Legacy endpoints survive for old URLs, and the SUPPORTED label changed in Unity 6000

Two pieces of maintenance history are documented and both are the kind of detail that only shows up in a README written by someone who has been running the site.

The first concerns URL compatibility. NoUnityCN v2 launched in June 2026 and restructured the site, but the endpoints /download, /component, /tools, /releaseNotses and /unityModule were kept so that old URLs continue to work. The README notes these endpoints exist only for legacy compatibility and are not used in the new pages. The spelling releaseNotses is preserved as written rather than corrected.

The second concerns Unity's own labelling. From the 6000 series, Unity uses the SUPPORTED label in place of TECH, and the site files SUPPORTED under the technical support section alongside TECH.

## A Radix and Tailwind app with a first run

The dependency list describes the interface layer rather than the service. It is built on React 19 types with a large set of Radix UI primitives, one package per component: accordion, alert-dialog, aspect-ratio, avatar, checkbox, collapsible, context-menu, dialog, dropdown-menu, hover-card, label, menubar, navigation-menu, popover, progress, radio-group, scroll-area, select, separator, slider, switch, tabs, toast, toggle, toggle-group and tooltip. Form tooling is present through @hookform/resolvers and cmdk, with class-variance-authority and clsx for class composition, and date-fns and embla-carousel-react for dates and carousels.

Analytics and tagging are third-party and worth noting before you deploy: @microsoft/clarity and @vercel/analytics are both dependencies, so a fork ships those integrations unless you remove them.

Locally the whole thing is pnpm install followed by one of the four dev or build commands. The declared requirement is Node.js 20 or newer, with pnpm as the recommended and default package manager, and npm, yarn and bun listed as alternatives. Both package-lock.json and pnpm-lock.yaml are present in the repository, which is a mild inconsistency worth cleaning if you fork it.

The top level also carries a .claude/ directory and components.json at the root, alongside app/, components/, hooks/, lib/, styles/ and public/.

## Licensing splits the code from the data

The copyright section is unusually careful and the split matters if you fork this. The software follows the MIT License and all code in the project is distributed under that agreement, but the licence does not cover content obtained through APIs, nor derivative content developed on the basis of the project.

In practice that means the code is reusable MIT, while the catalogue it displays is not yours to redistribute. A fork serving a different audience inherits the code licence and not the data.

The trademark paragraph is separate and standard: Unity, the Unity logo and other Unity marks belong to Unity Technologies or its branches, NoUnityCN is not a service provided by Unity Technologies, and the site's logo rights remain with Unity Technologies.

## Conclusion

Adopt this repository if you want to run your own Unity Editor version index, or if you specifically need a Next.js app that also deploys to Cloudflare Workers through vinext. Do not treat it as a download mirror, since the README states it stores no data, is not a cracking or modification tool, and provides no technical authorisation files such as activation licences, and it excludes developers in Greater China who are directed to the local Tuanjie engine instead. Verify first where your downloads actually come from, because the README attributes the download service to a separate public-benefit proxy project and warns it may be interrupted without notice.

## FAQ

### What does NoUnityCN provide and what does it not provide?

The README describes it as a version search service built on Unity's official public interfaces, using official public interfaces and retaining no data. It states it provides no technical authorisation files such as activation licences.

### How do I run NoUnityCN locally?

With Node.js 20 or newer, run pnpm install and then pnpm dev for the Next.js version on port 3000, or pnpm dev:vinext for the vinext version on port 3001.

### What do I need before deploying NoUnityCN to Cloudflare Workers?

The README lists a Worker whose name matches the name in wrangler.jsonc, a KV Namespace whose id replaces kv_namespaces[].id, Image Resizing enabled in the Worker settings if image optimisation is used, and a bound custom domain. Then pnpm exec vinext deploy or pnpm exec wrangler deploy.

### Which developers is NoUnityCN aimed at?

The README states it targets overseas developers working in China, developers using Chinese as their working language, and developers needing remote assistance. It explicitly does not serve developers in Greater China, who are recommended the Tuanjie engine instead.

### Can I reuse the NoUnityCN code in my own project?

The code is distributed under the MIT License, but the licence does not cover content obtained through APIs or derivative content based on the project, and Unity trademarks remain with Unity Technologies.

## Sources

- [DanKE123abc/NoUnityCN on GitHub](https://github.com/DanKE123abc/NoUnityCN)
- [License: MIT](https://github.com/DanKE123abc/NoUnityCN/blob/main/LICENSE)
- [Project website](https://nounitycn.danke666.top)
- [README](https://github.com/DanKE123abc/NoUnityCN/blob/main/README.md)
- [Releases](https://github.com/DanKE123abc/NoUnityCN/releases)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/danke123abc-nounitycn