yes

$ mkdir pd-unassert
$ cd pd-unassert
$ npm init -y
Wrote to /Users/takuto/work/pd-unassert/package.json:

{
  "name": "pd-unassert",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "keywords": [],
  "author": "",
  "license": "ISC"
}


$ npm install --save-dev unassert-cli
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN pd-unassert@1.0.0 No description
npm WARN pd-unassert@1.0.0 No repository field.

+ unassert-cli@1.0.0
added 43 packages from 130 contributors and audited 43 packages in 3.71s

9 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

$ cat <<EOT >> prod.js
heredoc> const assert = require('assert');
heredoc> function fail() {
heredoc>   throw new Error('fail');
heredoc> }
heredoc> assert.doesNotThrow(function () {
heredoc>   fail();
heredoc> });
heredoc> EOT
$ cat prod.js
const assert = require('assert');
function fail() {
  throw new Error('fail');
}
assert.doesNotThrow(function () {
  fail();
});
$ npx unassert prod.js
function fail() {
    throw new Error('fail');
}
$

Won't work for sub functions #18

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions