ThinkJS is a pnpm monorepo root with a four command README
Use full ES2015+ features to develop Node.js applications, Support TypeScript.
At a glance
- What is it?
- ThinkJS is a Node.js framework, MIT licensed and written in JavaScript. Its README is four commands and a console sample, but the root package.json tells a more current story: pnpm workspaces, Node 20.19 or newer, and a test script that skips three packages.
- Who is it for?
- ThinkJS fits a team already committed to pnpm workspaces and Node 20.19 or newer who wants to develop Node.js applications in JavaScript or TypeScript. It fits badly if you need current documentation: the README ends at `npm start`, and the newest listed release tag is v3.2.13 from 2020-12-16.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 2 days ago.
- What is it written in?
- Mainly JavaScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- thinkjs/thinkjs5,262 ★ · -5
| Repository | 2026-09-23 | 2026-11-15 |
|---|---|---|
| thinkjs/thinkjs | 5.3k | 5.3k |
-5 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The root package.json is private and not the published package
The most surprising field in the root manifest is `"private": true`. That means this package is never published to npm; it exists to hold scripts for the workspace. Its own `"version": "1.0.0"` is a placeholder and has no relationship to framework versions, so do not read 1.0.0 as a release number. Everything published lives under `packages/`, and the repo root confirms it with `pnpm-workspace.yaml`, `pnpm-lock.yaml` and the `packages/` directory itself. Reading the root manifest as if it were the shipped package leads to the wrong conclusion about what you get from a registry. The three script entries it holds, `test`, `coverage` and `lint`, all operate on `./packages/**` rather than on the root, which confirms that the root is a control plane. Its devDependencies, `@eslint/js`, `c8`, `eslint`, `globals` and `pre-commit`, are tooling for maintaining the workspace, not dependencies any consumer installs.
pnpm 11.6.0 is declared as the package manager
The manifest pins `"packageManager": "[email protected]"`, so the toolchain is pnpm rather than npm, and the version is pinned to a patch release. The lockfile is `pnpm-lock.yaml`, which is pnpm specific and will not be read by npm or yarn. That creates a mismatch with the README, which documents the project flow using npm commands:
npm install -g think-clithinkjs new demonpm installBoth work at the level of install and run, but a contributor working in this repository should let pnpm drive the workspace, since the scripts are all written as `pnpm` invocations.
The test script deliberately excludes three cache and store packages
The whole test entry point is one recursive command with three filters:
"test": "pnpm -r --if-present --filter './packages/**' --filter '!think-cache-memcache' --filter '!think-memcache' --filter '!think-mongo' test"Three packages are named and excluded: `think-cache-memcache`, `think-memcache` and `think-mongo`. The manifest does not say why they are excluded. The consequence for you is that a green test run says nothing about those three adapters. `--if-present` also means a workspace package without a test script is skipped silently.
Coverage runs through c8 and lint runs through eslint 10
Two more scripts show the shape of the tooling. `"coverage": "c8 pnpm test"` wraps the same recursive test run in c8, with configuration in the `.c8rc.json` file at the root and `codecov.yml` alongside it for upload. `"lint": "pnpm -r --if-present --filter './packages/**' lint"` walks the workspace and runs whatever lint script each package exposes. Dev dependencies are `@eslint/js ^10.0.1`, `eslint ^10.8.0`, `globals ^17.9.0`, `c8 ^12.0.0` and `pre-commit ^1.2.2`. Lint configuration is flat config style, in `eslint.config.cjs`, and `globals` supplies the environment definitions it reads. The presence of a pre-commit dependency means a local commit can be rejected by lint before it reaches CI, and `.gitmodules` at the root hints that at least part of the tree arrives as a submodule rather than as tracked files.
Node 20.19.0 is the declared engine floor
The `engines` block requires `"node": ">=20.19.0"`, which is a specific patch level rather than a major version. Anything older will not satisfy the declaration. The root is `"Programming Language :: JavaScript"` in effect through its own sources, and the project description states that full ES2015+ features are used to develop Node.js applications with TypeScript support. Node 20.19 or newer is also consistent with the dependency set: eslint 10 and c8 12 both expect a current runtime. If your CI pins an older Node image, the install step is where this shows up first.
Release tags stop at v3.2.13 in December 2020
The tag history is the part worth weighing. The newest release is v3.2.13, dated 2020-12-16, and the two before it are 2.1.3 and 2.1.2, both dated 2016-01-22. A gap of nearly five years between the 2.x tags and the 3.x tag suggests the project changed shape once and then stopped cutting releases, even though the repository itself is not archived and its last recorded push is 2026-10-18. Recent commits are therefore not the same as recent releases: the master branch moves while no new tag has appeared since 2020. If you are pinning a dependency, you are pinning 2020 code with a maintained dependency tree, which is a different risk profile from a released and current version.
What the README never explains about MVC structure
Four commands and a console sample is the entire README. It does not show a controller, a model, a route definition, or where configuration lives. The only runtime evidence offered is the startup log, which names the port, the framework version, the environment and the worker count:
[2017-05-22 15:54:58.281] [INFO] - Server running at http://127.0.0.1:8360
[2017-05-22 15:54:58.283] [INFO] - ThinkJS version: 3.0.0-alpha1
[2017-05-22 15:54:58.283] [INFO] - Environment: development
[2017-05-22 15:54:58.284] [INFO] - Workers: 1That sample predates v3.2.13 by years and reports an alpha version, so treat the port and worker defaults as historical. Everything about directory conventions and config files has to come from thinkjs.org/en or the Chinese documentation linked as README_zh-CN.md. The port in that sample, 8360, is the one number you can treat as a default hint rather than as history.
Editorial conclusion
ThinkJS fits a team already committed to pnpm workspaces and Node 20.19 or newer who wants to develop Node.js applications in JavaScript or TypeScript. It fits badly if you need current documentation: the README ends at `npm start`, and the newest listed release tag is v3.2.13 from 2020-12-16. Before adopting it, read thinkjs.org/en for the routing and model conventions the README omits, and confirm your CI can drive pnpm recursive test scripts with the three excluded packages.
Frequently asked questions
How do I install and start a ThinkJS application?
Install the CLI globally with `npm install -g think-cli`, scaffold a project with `thinkjs new demo`, install its dependencies with `npm install`, then start it with `npm start`.
Which Node.js version does the ThinkJS repository require?
The root package.json sets engines to node >=20.19.0, and it declares [email protected] as its package manager, so contributors work inside a pnpm workspace rooted at the repository.
Does ThinkJS support TypeScript?
The project description states it supports TypeScript and encourages use of full ES2015+ features when developing Node.js applications. The README does not show a TypeScript setup example.
Which ThinkJS packages are skipped when the tests run?
The recursive test script filters out three packages by name: think-cache-memcache, think-memcache and think-mongo.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/thinkjs-thinkjs)Star history chart for your README
[](https://hysenlabs.com/projects/thinkjs-thinkjs)Was this useful?