k6/x/sm JavaScript module registration disabled due to #30

[szkiba]

The k6/x/sm JavaScript module registration disabled due to #30

[nadiamoe]

Hey Ivan, thanks for your PR.

This k6/x/sm JavaScript module is apparently an experimental development

This is definitely not the case, Synthetic monitoring runs this extension in production tens of times per second to run scripted checks.

Regarding the changes in the PR, I'm not sure what are the effects of commenting those lines. Does the extension still function as an output by doing that? (I suspect yes, as the integration test passed on this PR, but would be good to confirm).

[szkiba]

Hey Nadia,

This k6/x/sm JavaScript module is apparently an experimental development

This is definitely not the case, Synthetic monitoring runs this extension in production tens of times per second to run scripted checks.

I wrote about the JavaScript module as experimental. xk6-sm is primarily an output extension and is used as such.

Regarding the changes in the PR, I'm not sure what are the effects of commenting those lines. Does the extension still function as an output by doing that? (I suspect yes, as the integration test passed on this PR, but would be good to confirm).

Of course it will continue to work as an output extension. The two registrations (JavaScript and Output) are independent of each other.

BTW If you look at the probe.go file you will see that it is an experiment (metric named foo_bar, debug messages etc).

[nadiamoe]

Ah, I see what you mean now. I don't think anything in the probe.go file is used or meant to be used in the short term, so we might just delete the file as well.

I have some work to do on this repo in the short term which will refactor how we handle metrics, but after that, I can take care of removing this for the time being.