Three separate findings from adopting dpctl in a React Native project. Filing together since they were hit in sequence; happy to split if you prefer.
(The slash crash that blocked releases is #6, not repeated here.)
1. deleteFolder(${os.tmpdir()}/react-*) never deletes anything
script/command-executor.ts:1364 clears the React Native bundler cache with a glob:
// This is needed to clear the react native bundler cache:
// https://github.com/facebook/react-native/issues/4289
.then(() => deleteFolder(`${os.tmpdir()}/react-*`))
v1.1.0 migrated to rimraf@^6, which dropped glob support — v6 treats the argument as a literal path. Verified:
const { rimraf } = require("rimraf"); // 6.1.3
fs.mkdirSync(path.join(os.tmpdir(), "react-globprobe"));
await rimraf(path.join(os.tmpdir(), "react-globprobe*"));
// directory still exists
Nothing fails loudly — the cleanup the comment describes simply stops happening, silently reintroducing react/react-native#4289.
A fix would resolve the glob first (glob + rimraf, or fs.readdir(os.tmpdir()) filtered by the react- prefix). Happy to send a PR if you have a preferred approach.
2. npm still serves 1.0.0, which cannot release at all
npm view @deploypulseio/dpctl versions returns only 1.0.0 (published 2025-12-31). GitHub is at v1.1.1.
1.0.0 declares rimraf: ^6.1.2 but calls the v2/v3 callback API:
// bin/script/command-executor.js:199
rimraf(folderPath, (err) => { ... }); // TypeError: rimraf is not a function
So npm i @deploypulseio/dpctl produces a CLI that fails before bundling even starts. The docs recommend installing from source, but the npm package exists and is what package managers resolve by default.
3. Docs reference an unpublished SDK package
https://docs.deploypulse.io/mobile says:
npm install @deploypulseio/react-native-code-push
That package name returns 404 on the npm registry.
Environment: Node v24.15.0, macOS, React Native 0.81.4.
Three separate findings from adopting dpctl in a React Native project. Filing together since they were hit in sequence; happy to split if you prefer.
(The
slashcrash that blocked releases is #6, not repeated here.)1.
deleteFolder(${os.tmpdir()}/react-*)never deletes anythingscript/command-executor.ts:1364clears the React Native bundler cache with a glob:v1.1.0migrated torimraf@^6, which dropped glob support — v6 treats the argument as a literal path. Verified:Nothing fails loudly — the cleanup the comment describes simply stops happening, silently reintroducing react/react-native#4289.
A fix would resolve the glob first (
glob+rimraf, orfs.readdir(os.tmpdir())filtered by thereact-prefix). Happy to send a PR if you have a preferred approach.2. npm still serves
1.0.0, which cannot release at allnpm view @deploypulseio/dpctl versionsreturns only1.0.0(published 2025-12-31). GitHub is atv1.1.1.1.0.0declaresrimraf: ^6.1.2but calls the v2/v3 callback API:So
npm i @deploypulseio/dpctlproduces a CLI that fails before bundling even starts. The docs recommend installing from source, but the npm package exists and is what package managers resolve by default.3. Docs reference an unpublished SDK package
https://docs.deploypulse.io/mobile says:
That package name returns 404 on the npm registry.
Environment: Node v24.15.0, macOS, React Native 0.81.4.