atao60 / fse-cli Goto Github PK

freephoenix888@freephoenix888:~/Programming/deep/create-typescript-npm-package-template$ npm i --save-dev @atao60/fse-cli

added 68 packages, and audited 139 packages in 10s

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

1 high severity vulnerability

To address all issues, run:
  npm audit fix

Run `npm audit` for details.

freephoenix888@freephoenix888:~/Programming/deep/create-typescript-npm-package-template$ npm audit fix

up to date, audited 139 packages in 2s

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

npm audit report

ansi-regex  5.0.0
Severity: high
Inefficient Regular Expression Complexity in chalk/ansi-regex - https://github.com/advisories/GHSA-93q8-gq69-wqmw
fix available via `npm audit fix`
node_modules/@atao60/fse-cli/node_modules/ansi-regex

1 high severity vulnerability

To address all issues, run:
  npm audit fix

Linux freephoenix888 5.19.0-42-generic #43~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Apr 21 16:51:08 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 22.04.2 LTS
Release:	22.04
Codename:	jammy

v18.14.0

0.1.7

14.16.0

^0.1.6

UnhandledPromiseRejectionWarning: Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only file and data URLs are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'c:'
    at Loader.defaultResolve [as _resolve] (internal/modules/esm/resolve.js:782:11)
    at Loader.resolve (internal/modules/esm/loader.js:86:40)
    at Loader.getModuleJob (internal/modules/esm/loader.js:230:28)
    at Loader.import (internal/modules/esm/loader.js:165:28)
    at importModuleDynamically (internal/modules/esm/translators.js:114:35)
    at exports.importModuleDynamicallyCallback (internal/process/esm_loader.js:30:14)

error @atao60/[email protected]: The engine "node" is incompatible with this module. Expected version "10.15.3". Got "12.14.0"
error Found incompatible module.

v12.16.1

"@atao60/fse-cli": "0.0.39",

npx fse-emptyDir ./build 
Be gone rapscalian...
(node:49264) UnhandledPromiseRejectionWarning: TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string or an instance of Buffer or URL. Received undefined
    at Object.readdir (fs.js:846:10)
    at go$readdir (/Volumes/Data/swagger-to-angular2/node_modules/@atao60/fse-cli/node_modules/graceful-fs/graceful-fs.js:202:23)
    at Object.readdir (/Volumes/Data/swagger-to-angular2/node_modules/@atao60/fse-cli/node_modules/graceful-fs/graceful-fs.js:184:12)
    at emptyDir (/Volumes/Data/swagger-to-angular2/node_modules/@atao60/fse-cli/node_modules/fs-extra/lib/empty/index.js:11:6)
    at emptyDir (/Volumes/Data/swagger-to-angular2/node_modules/@atao60/fse-cli/node_modules/universalify/index.js:5:57)
    at Object.job (/Volumes/Data/swagger-to-angular2/node_modules/@atao60/fse-cli/src/tasks/emptyDir.ts:33:5)
    at doit (/Volumes/Data/swagger-to-angular2/node_modules/@atao60/fse-cli/src/wrapper.ts:11:12)
    at cli (/Volumes/Data/swagger-to-angular2/node_modules/@atao60/fse-cli/src/cli.ts:6:5)
(node:49264) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:49264) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Checking if existing and, if not, creating directory dist/css ...
Directory dist/css exists.