Unitech / Unitech/pm2

Yarn 3.5.0 may disable pm2

Open
#5,597 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
43.3k
Forks
2.7k
PR merge metrics
No merged PRs in 30d

Description

When I use yarn to install node_modules for a node.js app, it caused pm2 to be disabled.
Still don't know why, but when I use npm install, it worked as usual.

Appreciate any suggestions or guides, thanks 🙏

root@TOP-APP:/home/Telebot# yarn
➤ YN0000: ┌ Resolution step
➤ YN0061: │ request@npm:2.88.2 is deprecated: request has been deprecated, see https://github.com/request/request/issues/3142
➤ YN0061: │ har-validator@npm:5.1.5 is deprecated: this library is no longer supported
➤ YN0061: │ request-promise@npm:4.2.6 is deprecated: request-promise has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
➤ YN0061: │ uuid@npm:3.4.0 is deprecated: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
➤ YN0061: │ @unimodules/core@npm:7.2.0 is deprecated: replaced by the 'expo' package, learn more: https://blog.expo.dev/whats-new-in-expo-modules-infrastructure-7a7cdda81ebc
➤ YN0061: │ @unimodules/react-native-adapter@npm:6.5.0 is deprecated: replaced by the 'expo' package, learn more: https://blog.expo.dev/whats-new-in-expo-modules-infrastructure-7a7cdda81ebc
➤ YN0002: │ isomorphic-webcrypto@npm:2.3.8 doesn't provide expo (pee784), requested by expo-random
➤ YN0002: │ isomorphic-webcrypto@npm:2.3.8 doesn't provide react-native (pa8d5a), requested by react-native-securerandom
➤ YN0000: │ Some peer dependencies are incorrectly met; run yarn explain peer-requirements <hash> for details, where <hash> is the six-letter p-prefixed code
➤ YN0000: └ Completed in 5s 487ms
➤ YN0000: ┌ Fetch step
➤ YN0013: │ y18n@npm:4.0.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yallist@npm:4.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yargs-parser@npm:18.1.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yargs@npm:15.4.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yocto-queue@npm:0.1.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0000: └ Completed in 1s 315ms
➤ YN0000: ┌ Link step
➤ YN0000: │ ESM support for PnP uses the experimental loader API and is therefore experimental
➤ YN0000: └ Completed in 3s 692ms
➤ YN0000: Done with warnings in 10s 593ms

Screen Shot 2023-05-05 at 10 05 26 PM

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the reported installation with Yarn 3.5.0 and compare it with npm install in a Node.js application using pm2. Start from the supplied Yarn output and screenshot; done means identifying why pm2 is disabled and documenting or correcting the behavior so the process manager remains usable after installation.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js
Domain
devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.