🐞 Bug: tsdx create generates outdated and Bun-incompatible project setup
Describe the Bug
Running bunx tsdx create <pkg-name> generates a project scaffold that relies on outdated and unmaintained TSDX internals. The generated package.json includes tsdx@^1.0.0, legacy scripts, and configurations that are not compatible with modern tooling, especially Bun.
As a result, bun install fails because Bun cannot resolve tsdx@^1.0.0, even though the package previously existed on npm. The generated output is out of sync with current best practices and modern build tools.
Steps to Reproduce
-
Run:
bunx tsdx create <pkg-name>
-
Navigate into the generated project
-
Run:
-
Observe the installation failure
Expected Behavior
Actual Behavior
error: No version matching "^1.0.0" found for specifier "tsdx"
error: tsdx@^1.0.0 failed to resolve
- The generated scripts (
tsdx dev, tsdx build, etc.) are unusable in Bun and rely on deprecated tooling.
Screenshots / Logs
bun install v1.2.19 (aad3abea)
error: No version matching "^1.0.0" found for specifier "tsdx"
error: tsdx@^1.0.0 failed to resolve
Environment
TSDX version: not installed (resolved via bunx)
Node version: v20.x.x
Bun version: 1.2.19
OS: macOS
Template used: default (React library)
Run used to collect versions:
echo "TSDX: $(bunx tsdx --version 2>/dev/null || echo 'not installed')"
echo "Node: $(node --version)"
echo "Bun: $(bun --version)"
echo "OS: $(uname -a)"
Additional Context
-
TSDX appears to be archived / unmaintained, but tsdx create still generates new projects without warning.
-
The generated configuration does not align with:
- Modern ESM standards
- Bun’s strict dependency resolver
- Current React library best practices
-
This leads to a broken first-time experience for users using Bun or modern Node tooling.
Suggestion:
- Deprecate
tsdx create, or
- Explicitly document that Bun is unsupported and the tool is legacy.
🐞 Bug:
tsdx creategenerates outdated and Bun-incompatible project setupDescribe the Bug
Running
bunx tsdx create <pkg-name>generates a project scaffold that relies on outdated and unmaintained TSDX internals. The generatedpackage.jsonincludestsdx@^1.0.0, legacy scripts, and configurations that are not compatible with modern tooling, especially Bun.As a result,
bun installfails because Bun cannot resolvetsdx@^1.0.0, even though the package previously existed on npm. The generated output is out of sync with current best practices and modern build tools.Steps to Reproduce
Run:
Navigate into the generated project
Run:
Observe the installation failure
Expected Behavior
The scaffolded project should:
tsup,vite, or Bun-compatible alternatives)package.jsonthat installs cleanly with modern runtimes (Node ≥20, Bun)Alternatively,
tsdx createshould warn that:Actual Behavior
The generated
package.jsonincludes:Running
bun installfails with:tsdx dev,tsdx build, etc.) are unusable in Bun and rely on deprecated tooling.Screenshots / Logs
Environment
Run used to collect versions:
Additional Context
TSDX appears to be archived / unmaintained, but
tsdx createstill generates new projects without warning.The generated configuration does not align with:
This leads to a broken first-time experience for users using Bun or modern Node tooling.
Suggestion:
tsdx create, or