➰ It's never been easier to try nodejs modules!

kinsi55 suggested on reddit that we could download and use multiple packages in one line. Something like this: trymodule lodash underscore and they would be assigned to lodash and underscore

Thanks for a great package to try out libraries (and the ipfs work)!

Several packages return Promise objects but when trying out libraries it would be nice to see what the Promise resolved to rather than just knowing that a Promise was returned. For example, if you run trymodule octokat and then enter (new octokat()).zen.read() in the REPL (which executes GET https://api.github.com/zen ) you get the following:

> (new octokat()).zen.read()
Promise { <pending> }
> 

With this code change you instead get the resolved Promise:

> (new octokat()).zen.read()
Returned a Promise. waiting for result...
'It\'s not fully shipped until it\'s fast.'
>

It seems libraries like es6-promise are still being actively downloaded (~250k/day) so I also included support for that

Btw, I stumbled upon this great package from http://www.thedotpost.com/2016/12/zeke-sikelianos-navigating-javascript-userland (thanks @zeke !)

Hey all 👋

I saw the discussion in #17 and decided to jump in.

Let's talk about these changes, and hopefully get them merged.

Changes:

• Implement custom variable feature
• flags and packages arrays to make adding more features a little easier
• return statements added to block-body arrow functions: per MDN, "The block body form doesn't automatically return a value. You need to use an explicit return statement."
• Packages are passed around as tuples before they're resolved in index.js, so we can keep track of both what the module's name is and what the user wants to assign it to.
• hasFlag and makeVariableFriendly functions were added.
• A test for the new functionality was added.

Using _ doesn't work on newer versions of node. See https://github.com/nodejs/node/issues/5431

❯ node -v   
v6.4.0

~/Desktop master*
❯ trymodule lodash=_
Gonna start a REPL with packages installed and loaded for you
'lodash' was already installed since before!
Package 'lodash' was loaded and assigned to '_' in the current scope
REPL started...
> Expression assignment to _ now disabled.

Maybe someone is used to calling lodash as _ in their code, we should allow them to specify this when starting trymodule.

Example

# trymodule [email protected]=_ [email protected]=underscorejs
Package 'lodash' was loaded and assigned to '_' in the current scope
Package 'underscorejs' was loaded and assigned to 'underscorejs' in the current scope

This was first brought up in https://github.com/VictorBjelkholm/trymodule/issues/13

This is a small change for replace unwanted characters of the package name, also ensures to replace all the occurrences of the string, so, having this name "abc-de.ab--.cde-":

Before "abc_de_ab--.cde-" Now "abc_de_ab___cde_"

Thanks for the module!

hi! I want to try out node-jira module which requires me to import the module like this JiraApi = require('jira').JiraApi;

I am unable to figure out how to run the same in trymodule node-jira.

I'm trying to get trymodule to persist the history between sessions but not sure what I'm doing wrong. I've opened a issue in nodejs/node, asking for help.

https://github.com/nodejs/node/issues/5730

https://github.com/VictorBjelkholm/trymodule/blob/2030806d790213d426456959fdc7a69773a4c6f7/index.js#L9 Use os.homedir().

From https://github.com/sindresorhus/awesome-nodejs/pull/477#event-606502245

I get this error when I try to run anything e.g. trymodule lodash:

Gonna start a REPL with packages installed and loaded for you
Couldn't find 'lodash' locally, gonna download it now
[email protected] .trymodule/node_modules/lodash
Package 'lodash' was loaded and assigned to 'l' in the current scope
REPL started...
  /usr/local/lib/node_modules/trymodule/node_modules/repl.history/index.js:19
  repl.rli.addListener('line', function(code) {
           ^

TypeError: Cannot read property 'addListener' of undefined
    at module.exports (/usr/local/lib/node_modules/trymodule/node_modules/repl.history/index.js:19:12)
    at /usr/local/lib/node_modules/trymodule/cli.js:72:7
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:94:5)

I've done basic clean up steps i.e. uninstall trymodule and delete the ~/.trymodule/ folder (or trymodule --clear).

I don't understand why it fails here.

Currently trymodule contains 41 vulnerabilities (35 moderate, 6 high) due to not updated packages. @victorb please update packages.

List of outdated packages with vulnerabilities:

Severity: Moderate Type: ReDoS
Package brace-expansion
Patched in >=1.1.7
Dependency of trymodule Path trymodule > npmi > npm > fs-vacuum > rimraf > glob > minimatch > brace-expansion
Path trymodule > npmi > npm > fstream-npm > fstream-ignore > minimatch > brace-expansion
Path trymodule > npmi > npm > node-gyp > fstream > rimraf > glob > minimatch > brace-expansion
More info https://nodesecurity.io/advisories/338

Severity: Moderate
Type: Prototype pollution Package hoek
Patched in > 4.2.0 < 5.0.0 || >= 5.0.3
Dependency of trymodule Path trymodule > npmi > npm > node-gyp > request > hawk > boom > hoek Path trymodule > npmi > npm > node-gyp > request > hawk > cryptiles > boom > hoek
Path trymodule > npmi > npm > node-gyp > request > hawk > hoek Path trymodule > npmi > npm > node-gyp > request > hawk > sntp > hoek
Path trymodule > npmi > npm > npm-registry-client > request > hawk > boom > hoek
Path trymodule > npmi > npm > npm-registry-client > request > hawk > cryptiles > boom > hoek
Path trymodule > npmi > npm > npm-registry-client > request > hawk > hoek
Path trymodule > npmi > npm > npm-registry-client > request > hawk > sntp > hoek
Path trymodule > npmi > npm > request > hawk > boom > hoek Path trymodule > npmi > npm > request > hawk > cryptiles > boom > hoek
Path trymodule > npmi > npm > request > hawk > hoek Path trymodule > npmi > npm > request > hawk > sntp > hoek More info https://nodesecurity.io/advisories/566

Severity: High
Type: Regular Expression Denial of Service
Package sshpk Patched in >=1.13.2 < 1.14.0 || >=1.14.1 Dependency of trymodule Path trymodule > npmi > npm > node-gyp > request > http-signature > sshpk
Path trymodule > npmi > npm > npm-registry-client > request > http-signature > sshpk
Path trymodule > npmi > npm > request > http-signature > sshpk More info https://nodesecurity.io/advisories/606

Severity: High
Type: Regular Expression Denial of Service Package tough-cookie
Patched in >=2.3.3 Dependency of trymodule Path trymodule > npmi > npm > node-gyp > request > tough-cookie Path trymodule > npmi > npm > npm-registry-client > request > tough-cookie
Path trymodule > npmi > npm > request > tough-cookie More info https://nodesecurity.io/advisories/525

Severity: Moderate
Type: Memory Exposure Package tunnel-agent Patched in >=0.6.0 Dependency of trymodule Path trymodule > npmi > npm > node-gyp > request > tunnel-agent Path trymodule > npmi > npm > npm-registry-client > request > tunnel-agent
Path trymodule > npmi > npm > request > tunnel-agent More info https://nodesecurity.io/advisories/598

Severity: Moderate
Type: Out-of-bounds Read Package stringstream Patched in >=0.0.6 Dependency of trymodule Path trymodule > npmi > npm > node-gyp > request > stringstream Path trymodule > npmi > npm > npm-registry-client > request > stringstream Path trymodule > npmi > npm > request > stringstream More info https://nodesecurity.io/advisories/664

Functions are objects and are valid thenables:

"promise" is an object or function with a then method whose behavior conforms to this specification. [1]

This PR uses is-promise to detect promises in a spec-compliant way.

[1] https://promisesaplus.com/#terminology

This uses the same approach as n_ (@borisdiakur++) to ensure that _ can safely be assigned and reassigned without:

• a warning: Expression assignment to _ now disabled.
• resulting in _ becoming undefined

Tested on:

• v4.0.0
• v4.2.1
• v4.8.1
• v6.10.1
• v7.8.0

Hey @VictorBjelkholm. I love this module!

It would be cool to be able to run trymodule . or trymodule some/dir to load a REPL for a given directory, using the name of the directory as the name of required module:

cd projects/foo
trymodule .

Then in the repl, foo would be set to the value of require('.')