-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Node packages should not be fetched #360
Comments
I have also some debug logs, and it seems my theory is not that far from reality:
|
There is a node package package that seems to have a list of built-in modules. |
Although you cannot import NodeJS API, you may use npm modules as described in the k6 Modules documentation. If you want to open a file, you can use the
|
Oh wow got it! Where is May I ask you the why of mixing the two worlds? In terms of usability it does seem a bit confusing I have to say. Or maybe I did not read the docs properly and this was written all along. In any case thanks a lot for the prompt response! |
Sorry for that, there is a documentation article pending of being published.
The Modules documentation describes that you have to browserify the npm module. Browserify will take care of the
JS as the scripting language for user adoption and
I think we have to improve our documentation/communication in this aspect. Thanks for the feedback. I am closing the issue, let us know if you have any other question here or in stackoverflow using |
@ppcano I tried
|
Hello all!
I am trying the following in my script:
but I receive:
It seems to me that the feature (I was reading issue #167) that fetches dependencies should skip fetching node built-in modules, but I might be doing something wrong instead.
Thanks for this, it looks very nice!
The text was updated successfully, but these errors were encountered: