Jmeter-to-k6 on windows


On Windows downloaded “GitHub - grafana/jmeter-to-k6: Converts JMeter .jmx files to k6 JS code” zip folder and installed nodejs and npm. When tried to convert getting error message. When tried to convert sample jmx files getting below error message.

node jmeter-to-k6.js C:\Users\hhanumanthappa\Documents\CSVDataSet.jmx -o C:\Users\hhanumanthappa\Documents\Ck6\test.js

(node:27288) UnhandledPromiseRejectionWarning: Error: EPERM: operation not permitted, symlink 'C:\Users\<<path>>\Downloads\jmeter-to-k6-master\jmeter-to-k6-master\node_modules' -> 'C:\Users\<path>~1\AppData\Local\Temp\tmp-27288vk7HpwHHQYPs\node_modules'
(Use `node --trace-warnings ...` to show where the warning was created)
(node:27288) 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 (rejection id: 1)
(node:27288) [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.


a quick google searched lead me to:
Windows: EPERM: operation not permitted, symlink · Issue #1969 · lovell/sharp · GitHub and how can use sharp in lambda function (OS: window10 , severless) · Issue #1671 · lovell/sharp · GitHub which suggest that either you are running on fat32 or that you need root cmd to run the command for some reason, not a windows user :man_shrugging: .

I would recommend using the docker image and if there are any more errors, it might be better to just open an issue with the jmeter-to-k6 project

The original concept of promises was that you could have a rejected promise sitting around for some time before attaching a catch handler to it. For example, Firefox used to warn of uncaught rejection errors only when a rejected promise with no rejection handler was garbage collected from memory.

Somebody decided that JavaScript programmers couldn’t be trusted with managing promise rejections properly and changed the HTML spec to require browsers to throw “unhandled promise rejection” errors if a rejected promise has no rejection handlers added before code returns to the event loop.

On a case by case basis you can prevent the host being notified by adding a rejection handler that is never used. The reasoning is that adding a dummy rejection handler to a promise means that should it be rejected it has a rejection handler already - or if it was rejected the host is notified the promise now has a rejection handler - and you can call then and catch multiple times on the same promise.

A nice way to wait for several Promises to resolve to use the Promise.all function. It expects an Array of Promises, and produces a Promise that resolves to an Array containing the values that the individual Promises resolved to. Furthermore, it only resolves after the last Promise resolves. If any of its input Promises rejects, then the entire Promise.all expression rejects as well. It effectively “runs” all of its input processes “at the same time”, emulating the classic “fork-join” pattern.