atlas cli - plugins folder not found
Timo972 opened this issue · 0 comments
Timo972 commented
if you want to use the atlas cli you have to manually create a folder named plugins in the directory you want to use.
Otherwise it throws this:
(node:15556) UnhandledPromiseRejectionWarning: Error: Path you want to find stuff in doesn't exist C:\Dev\plugins
at generatePathDoesntExistError (C:\Users\timo972\AppData\Roaming\npm\node_modules\@abstractflo\atlas-cli\node_modules\fs-jetpack\lib\find.js:49:15)
at Object.findSyncInit [as sync] (C:\Users\timo972\AppData\Roaming\npm\node_modules\@abstractflo\atlas-cli\node_modules\fs-jetpack\lib\find.js:100:11)
at Object.find (C:\Users\timo972\AppData\Roaming\npm\node_modules\@abstractflo\atlas-cli\node_modules\fs-jetpack\lib\jetpack.js:138:19)
at bootstrap (file:///C:/Users/timo972/AppData/Roaming/npm/node_modules/@abstractflo/atlas-cli/dist/atlas-cli.esm.mjs:1691:39)
at file:///C:/Users/timo972/AppData/Roaming/npm/node_modules/@abstractflo/atlas-cli/dist/atlas-cli.esm.mjs:1735:1
at ModuleJob.run (internal/modules/esm/module_job.js:152:23)
at async Loader.import (internal/modules/esm/loader.js:166:24)
at async Object.loadESM (internal/process/esm_loader.js:68:5)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:15556) 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:15556) [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.
In this case i wanted to use the atlas cli in C:\Dev