Skip to content

tool creation script bug #181

@ShahafShavit

Description

@ShahafShavit

Is the script able to run in windows development environments?
I am running into trouble seconds after cloning, trying to create a tool.

PS C:\DEV\omni-tools> npm run script:create:tool set-operations list

omni-tools@0.1.0 script:create:tool
node scripts/create-tool.mjs set-operations list

node:fs:1363
const result = binding.mkdir(
^

Error: ENOENT: no such file or directory, mkdir 'C:\DEV\omni-tools\C:'
at Object.mkdirSync (node:fs:1363:26)
at recursiveCreate (file:///C:/DEV/omni-tools/scripts/create-tool.mjs:36:10)
at createFolderStructure (file:///C:/DEV/omni-tools/scripts/create-tool.mjs:57:3)
at file:///C:/DEV/omni-tools/scripts/create-tool.mjs:65:7
at ModuleJob.run (node:internal/modules/esm/module_job:329:25)
at async onImport.tracePromise.proto (node:internal/modules/esm/loader:644:26)
at async asyncRunEntryPointWithESMLoader (node:internal/modules/run_main:117:5) {
errno: -4058,
code: 'ENOENT',
syscall: 'mkdir',
path: 'C:\DEV\omni-tools\C:'
}

Node.js v22.17.0

the script is malfunctioning for some reason, something in the way it handles the folder structure and figures out where it is stored.
just a quick glance at the creation script- seems not very robust way of doing that if i may say..

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions