Heya! I'm Kat, the architect for the npm CLI and tink. I just wanted to let you know that your project is super cool and I think is a fantastic candidate for replacing the current npm search (starting off as the new tink search). I've made a post about it asking for community collaborators to contribute it, and I'm expecting a variation on your project!

This isn't me writing asking for you to contribute it, by the way. I just wanted to make sure you knew and hopefully were happy to have inspired this improvement. Thanks for the cool project!

Hi,

First of all, great project!

I'm using yarn in some projects and npm in other. emma is however defaulting to yarn due to these lines:

What do you think of checking if package-lock.json exist first? Something like

const canAccessFile = promisify(fs.access)
const exec = promisify(child_process.exec)

const isYarnInstalled = () => exec(`yarnpkg --version`, { stdio: `ignore` }).then(() => true).catch(() => false)

const shouldUseYarn = () => {
  return canAccessFile('package-lock.json')
    .then(() => false)
    .catch(isYarnInstalled)
}

And then:

- const yarn = shouldUseYarn()
+ const yarn = await shouldUseYarn()

I can create a pull request if you want.

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

• Update dependency @prisma/photon to v2.0.0-preview019
• Update dependency @types/object-hash to v1.3.4
• Update dependency @types/supertest to v2.0.16
• Update dependency creato to v1.1.4
• Update dependency ink-testing-library to v1.0.3 (ink-testing-library, @types/ink-testing-library)
• Update dependency multilines to v1.0.3
• Update dependency multilines to v1.0.3
• Update dependency pretty-quick to v2.0.2
• Update dependency prisma2 to v2.0.0-preview025
• Update dependency prisma2 to v2.0.0-preview025
• Update dependency rimraf to v3.0.2
• Update dependency string-width to v4.2.3
• Update dependency @types/jest to v24.9.1
• Update dependency @types/lodash to v4.17.0
• Update dependency ink to v2.7.1
• Update dependency ink-spinner to v3.1.0
• Update dependency js-yaml to v3.14.1 (js-yaml, @types/js-yaml)
• Update dependency nock to v11.9.1
• Update dependency node-fetch to v2.7.0 (node-fetch, @types/node-fetch)
• Update dependency object-hash to v2.2.0
• Update dependency open to v7.4.2
• Update dependency ora to v4.1.1
• Update dependency prompts to v2.4.2 (prompts, @types/prompts)
• Update dependency ts-node-dev to v1.1.8
• Update react monorepo (@types/react, react)
• Update dependency @types/algoliasearch to v4
• Update dependency @types/jsonwebtoken to v9
• Update dependency @types/meow to v6
• Update dependency @types/node to v20
• Update dependency @types/supertest to v6
• Update dependency @types/update-notifier to v6
• Update dependency algoliasearch to v4
• Update dependency chalk to v5
• Update dependency cli-truncate to v4
• Update dependency execa to v8
• Update dependency husky to v9
• Update dependency ink to v4
• Update dependency ink-spinner to v5
• Update dependency ink-testing-library to v3
• Update dependency js-yaml to v4 (js-yaml, @types/js-yaml)
• Update dependency lerna to v8
• Update dependency meow to v13
• Update dependency nock to v13
• Update dependency node-fetch to v3
• Update dependency object-hash to v3 (object-hash, @types/object-hash)
• Update dependency open to v10
• Update dependency ora to v8
• Update dependency pkg to v5
• Update dependency prettier to v3
• Update dependency pretty-quick to v4
• Update dependency rimraf to v5
• Update dependency string-width to v7
• Update dependency supertest to v7
• Update dependency ts-node to v10
• Update dependency ts-node-dev to v2
• Update dependency tslint to v6
• Update dependency typescript to v5
• Update dependency update-notifier to v7
• Update jest monorepo to v29 (major) (@types/jest, jest, ts-jest)
• Update react monorepo to v18 (major) (@types/react, react)
• 🔐 Create all rate-limited PRs at once 🔐

Edited/Blocked

These updates have been manually edited so Renovate will no longer make changes. To discard all commits and start over, click on a checkbox.

• Update dependency codecov to v3.6.2 [SECURITY]
• Update dependency lodash to v4.17.21 [SECURITY]
• Update dependency @types/algoliasearch to v3.34.11
• Update dependency @types/update-notifier to v2.5.2
• Update dependency @zeit/ncc to v0.22.3
• Update dependency execa to v3.4.0
• Update dependency husky to v3.1.0
• Update dependency lerna to v3.22.1
• Update dependency pkg to v4.5.1
• Update dependency ts-jest to v24.3.0
• Update dependency ts-node to v8.10.2
• Update dependency typescript to v3.9.10

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• Update dependency express to v4.19.2 [SECURITY]
• Update dependency jsonwebtoken to v9 [SECURITY]
• Update dependency probot to v12 [SECURITY]
• Update dependency @types/express to v4.17.21
• Update dependency @types/jsonwebtoken to v8.5.9
• Update dependency @types/node to v12.20.55
• Update dependency fp-ts to v2.16.5
• Update dependency io-ts to v2.2.21
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Fresh install, running emma

~/.config/yarn/global/node_modules/emma-cli/node_modules/ink/lib/diff.js:32
                vnode.createInstance(props);
                      ^

TypeError: vnode.createInstance is not a function

5 results is really to limited IMO.
If I don't already know the exact package name, I can't really get a list long enough to maybe find the right-one. Feel free to close or keep it as nice to have as it's really a personal opinion.

Hey @maticzav, thanks for this awesome tool 👍

This is just a suggestion, not really an issue, but it would be great if we could see the packages version in the search list!

What do you think?

Hi, awesome project

I see that we can choose to install packages as devDependencies with the --dev option, but often what happens to me is i search for a package like yarn add next react react-dom and then need to do yarn add -D @types/next @types/react @types/react-dom as a devDependencies.

I see two way your cli would be awesome, first i can just start searching and when i select a package to install their is some way to choose as a dependencies or devDependencies so i don't have to to quit the search to switch between dev and normal dependencies.

The second way that would be even more awesome is only useful for typescript people but that would be to install as devDependencies the @types package automatically by searching if it exist.

Let me know how that sounds to you and maybe we can work something out :)

Love the tool! One thing you might want to consider looking into is a way to select more than one package at a time with a search. For instance, if I want both react and react-dom, I type in react and both come up. However, I have to press enter on React, retype react, arrow down to react-dom, press enter, then press enter again just to install 2 packages. If I wanted eslint-react-plugin as well, it'd be even worse.

Instead, if I could press space bar or similar to multi-select current packages on the screen, it would make this great tool even quicker. Thanks!

You might want to give a look at the code too, though. I often find so-called micro packages and then find out that they have huge or useless dependencies. Gotta read that index.js!
https://twitter.com/bfred_it/status/971684338549977089

I like to run a custom script to install my node packages. Is there a way to set the command that is used for installation or just get the output as something machine parseable?

Hi there,

Thank you so much for creating this tool, it looks awesome! However, after I install it, by running npm install -g emma-cli, everytime I enter emma, I get the following error:

const canAccessFile = (0, _util.promisify)(_fs.default.access);
                                          ^

TypeError: (0 , _util.promisify) is not a function
    at Object.<anonymous> (/usr/local/lib/node_modules/emma-cli/dist/emma.js:40:43)
    at Module._compile (module.js:570:32)
    at Object.Module._extensions..js (module.js:579:10)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)
    at Function.Module._load (module.js:438:3)
    at Module.require (module.js:497:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (/usr/local/lib/node_modules/emma-cli/dist/index.js:10:36)
    at Module._compile (module.js:570:32)```

After yarn global add emma-cli.
I got a successful message:

success Installed "[email protected]" with binaries:
      - emma
      - ema
✨  Done in 3.96s.

But no emma CLI is at ls /usr/local/bin/.
Other yarn packages installed globally are present there.

Using npx works great 👍

My env is:

• macos Mojave
• hyper term with fish 3.0.2
• yarn 1.5.1
• node 10.15.3

🤔