Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 00:30
    zkochan commented #1221
  • Oct 20 23:03

    zkochan on v5.10.0

    (compare)

  • Oct 20 23:03

    zkochan on master

    chore(release): 5.10.0 (compare)

  • Oct 20 22:17

    zkochan on 2942

    (compare)

  • Oct 20 22:17

    zkochan on master

    feat: script-shell close #2942… (compare)

  • Oct 20 22:17
    zkochan closed #2942
  • Oct 20 22:17
    zkochan closed #2943
  • Oct 20 21:13
    zkochan labeled #2943
  • Oct 20 21:13
    zkochan milestoned #2943
  • Oct 20 21:13
    zkochan review_requested #2943
  • Oct 20 21:09
    zkochan commented #2863
  • Oct 20 20:57
    whitecolor commented #2863
  • Oct 20 20:56
    whitecolor commented #2863
  • Oct 20 20:56
    whitecolor commented #2863
  • Oct 20 20:55
    whitecolor commented #2863
  • Oct 20 20:50
    zkochan synchronize #2943
  • Oct 20 20:50

    zkochan on 2942

    test: script-shell (compare)

  • Oct 20 20:25
    zkochan synchronize #2943
  • Oct 20 20:25

    zkochan on 2942

    feat: script-shell (compare)

  • Oct 20 20:09
    zkochan opened #2943
arri-cc
@arri-cc
while rush only expects values without the @ prefix
2 replies
Divyanshu Verma
@vermadivyanshu

i am trying solve a buggy package which uses https but does not list it in its depedencies
https://github.com/visionmedia/superagent/blob/2fcea621c69e3cc779bc59f5f3e8677c2cce8f99/src/node/index.js#L8
I used the readPackage and added the dependency:

case 'superagent':
      pkg.dependencies['https'] = '^1.0.0';
      break;

It is added in the pnpm-lock.yaml file in the dependencies, but i still get the error:
Error: Unable to resolve module https from ../../node_modules/_pnpm/superagent/3.8.3/node_modules/superagent/lib/node/index.js
can someone point me in the correct direction how to debug this? or am i missing something ?

2 replies
arpitprod
@arpitprod
How to build react project after install ?
my builder is parcel and I tried with this command pnpm build
NODE_ENV=production parcel build public/index.html --no-source-maps
arpitprod
@arpitprod
Screenshot 2020-07-09 at 7.13.55 PM.png
it's showing this error, and I removed package-lock.json file and node_modules/ directory and run pnpm install && pnpm build command again
arpitprod
@arpitprod
Screenshot 2020-07-09 at 7.31.49 PM.png
it's showing this error now
How to solve this error ?
Juan Picado
@juanpicado

I’m doing an experiment and perhaps you here I can get some light

{
  "name": "pnpm_test",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "build": "babel --help",
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "keywords": [],
  "author": "",
  "license": "ISC",
  "devDependencies": {
    "@verdaccio/babel-preset": "^9.7.1",
    "typescript": "^3.9.6"
  }
}

my dependency @verdaccio/babel-preset has babel as dependency but I don’t see it on my .bin folder, but I see Typescript for instance. Does anyone knows why?

Screen Shot 2020-07-11 at 5.45.49 PM.png
I can se babel few levels down … but I don’t manage to access to it with the pnpm command.
➜ pnpm run build

> pnpm_test@1.0.0 build /Users/jpicado/WebstormProjects/pnpm_test
> babel --help

sh: babel: command not found
 ERROR  Command failed.
6 replies
Zoltan Kochan
@zkochan
We will probably be switching to a Discord platform because Gitter has many issues 😕
I created this room: https://discord.gg/mThkzAT
Christos
@ChristosChristofidis
hi
what kind of issues?
5 replies
Jacky Efendi
@jackyef
Hi, guys. I have a question. I am currently moving to node 12 using nvm. I see that I need to install pnpm again for each version of node installed on my machine using nvm
When I install a package globally, pnpm install -g, it installs the package to a different pnpm-global directory, which is what I expect
But, when I install dependencies on my existing project, it reuses the modules in the existing .pnpm-store (which was populated when I was using node v10)
My question is, is this a safe behavior? Could I possibly face an issue with a project running on node 12 uses incompatible modules built for node 10? Or will the build step (postinstall, etc) be run everytime I run pnpm install so it doesn't really matter that it uses the same .pnpm-store?
9 replies
bodqhrohro
@bodqhrohro
How to properly do npm install --save babel-runtime/core-js/object/keys with pnpm? It tries to look for a such path in the project directory rather than installing a submodule o_O
2 replies
Bruno Parga
@brunoparga

Hey everyone! I'm running into an issue with pnpm and the vscode-eslint plugin. ESLint was supposed to run automatically, but when it tries to run I get this error:

(node:97815) UnhandledPromiseRejectionWarning: Error: Command failed: pnpm root -g
 ERROR  No write access to the found global executable directories

    at checkExecSyncError (child_process.js:634:11)
    at Object.execSync (child_process.js:670:15)
    at Object.execSync (electron/js2c/asar.js:696:23)
    at Object.get (/home/bruno/.vscode-oss/extensions/dbaeumer.vscode-eslint-2.1.5/server/out/eslintServer.js:1:33524)
(...)

I suspect the error is on the plugin side, and I am also opening an issue there, but I thought of asking here as well due to VSCode's recent (v 1.47) addition of official support for pnpm. I actually use VSCodium, if that makes a difference.

Any ideas for how to make the extension and pnpm work together alright?

10 replies
Daniel A.C. Martin
@daniel-ac-martin
Hi.
Does anyone know if there is a way I can consume my pnpm-based monorepo without publishing? I had hoped to consume it via Git for a while until it was a little more stable. However, I realised that the workspace: references wouldn't resolve.
Zoltan Kochan
@zkochan
just release snapshot versions with changesets
the published packages will have versions like: 0.0.0-<hash>
enricofadly
@enricofadly
anyone know how to use pnpm to install dependecies when i run pnpx eslint --init
Ryan Festag
@rfestag
Is anyone else having issues with pnpm and nextjs/react? Up until recently, I could easily use pnpm init next-app, blow away the node_modules directory and the package-lock.json, then re-install with pnpm, and everything would work. Now, when I do those same steps (or I even just try to install next from scratch in a clean directory), trying to run next dev causes the Error: Invalid hook call. Hooks can only be called inside of the body of a function component error. Using npm instead of pnpm works fine for the exact same code.
5 replies
Zefex
@zefexdeveloper_twitter
I'm totally new to pnpm and also not a expert regarding deployment so I was wondering, what is the best way to deploy a monorepo? My project right now is using yarn workspaces, one package has next.js, the other one is nodejs with graphql an other things, there's also packages for common things and they are all using typescript as well... Can anyone help me perhaps migrate to pnpm if it allows me handling the monorepo easier and deploying it? I would appreciate any advice, article or anything.
Vsevolod Rodionov
@Jabher

Hi. I'm trying to make pnpm work with artifactory, but I got stuck.
PNPM attempts to fetch https://mydomain/artifactory/api/npm/fcc-d-npm/@fcc/icons/-/@fcc/icons-1.23.3.tgz, however, npm package tarball is actually at
https://mydomain/artifactory/fcc-d-npm/%40fcc/icons/-/%40fcc/icons-1.23.3.tgz

Is it artifactory bug? Or pnpm bug? NPM works fine with this

1 reply
cаввидис
@panoply
@zkochan enable github sponsors for yourself.
2 replies
Kib Vindas
@kvindasAB
Hello Guys, quick question. I'm trying to migrate a monorepo from Lerna to Pnpm. The issue that I have is that pnpm is installing some packages at the root of the monorepo, which creates double version of some typescript typings.
Anyone know why is pnpm doing that? I understood that root node_modules should not contain any visible packages.
11 replies
Fen Walker
@Madebyfen
Hello! We currently have an issue with PNPM where we're getting cross-package type errors. It appears that some @types packages declare types on the global scope and these ambient declarations are picked up from the project root(?) As an example, we have a Node package which is showing type errors from an e2e automation package, which has a dependency on JQuery types. Window does not exist globally in the Node package so the JQuery type declarations trigger errors. Ideally these types shouldn't affect packages that don't depend on them. Is there some strategy we're missing? Any help much appreciated :)
5 replies
mjolnir91
@mjolnir91
@rfestag just ran into the same issue. Switch to npm works fine switch back to pnpm it fails. Tried to flatten didn't fix it. Probably just going to stick with npm till someone figured out the issue.
Zefex
@zefexdeveloper_twitter
@zkochan How is the Next.js support? I saw a few issues back from 2017 but they are still not fixed and I just tried to install and run using pnpm and all I have is errors. It's really sad to be forced to drop pnpm cause of that :(
7 replies
matrixbot
@matrixbot
Resynth (@resynth1943:fairydust.space) Does PNPM have an account on Mastodon?
Resynth (@resynth1943:fairydust.space) Would be nice for the millions of people on the fedi to be able to keep up with the project
Ryan Festag
@rfestag
I just tried the 5.5.4 baseline, and it looks like the behavior of --parallel and/or --stream changed. The output falls back to the standard pnpm output that doesn't show each application on its own line interleaved and prefixed. Is that expected? Falling back to 5.5.3 works as expected
2 replies
Itay Mendelawy
@itaymendel

Hi all! I got a newbie questions... I'm trying to install a global package and keep getting this error.. wasn't able to find anything online about it

 ERROR  This modules directory was created using the following registries configuration: {"default":"https://registry.npmjs.org/"}. The current configuration is {"default":"https://registry.npmjs.org/","@bit":"https://node.bit.dev/"}. To recreate the modules directory using the new settings, run "pnpm install".

this is probably have to do with the fact that i've edited ~/.npmrc and logged in to another registry

1 reply
Zoltan Kochan
@zkochan

@/all please post in our Discord channels instead of Gitter

use this link to join:
https://discord.gg/mThkzAT

Vasiliy Yorkin
@vyorkin
https://gitter.im/pnpm/pnpm?at=5cc23e473b6cb0686a52fa9d I think I have the same issue with pnpm 5.5.10
WARN  Cannot link dependency with name webpack to /files/projects/foo/common/temp/node_modules/.pnpm/webpack@4.44.1_webpack@4.44.1/node_modules. Dependency's name should differ from the parent's name.
matrixbot
@matrixbot

Resynth > <@gitter_zkochan:matrix.org> @/all please post in our Discord channels instead of Gitter

use this link to join:
https://discord.gg/mThkzAT

No offence but it really comes to something when people like you throwaway a perfectly fine open-source product for a restrictive, hostile closed-source platform, which isn't, in any way, in the spirit of FOSS

Resynth * No offence but it really comes to something when people like you throw away a perfectly fine open-source product for a restrictive, hostile closed-source platform, which isn't, in any way, in the spirit of FOSS
Resynth Sorry, it just annoyed me
Resynth Honestly it's just so disheartening to see open-source development being locked away behind these horrendous platforms. The people that refuse to use them (for privacy reasons) miss out. So it's either privacy or development. Gosh.
matrixbot
@matrixbot
Resynth * Honestly it's just so disheartening to see open-source development being locked away behind horrendous platforms like Discord. The people that refuse to use them (for privacy reasons) miss out. So it's either privacy or development. Gosh.
Zoltan Kochan
@zkochan
using discord is not obligatory. If someone doesn't want to use it, just use Github issues. I did a poll on Twitter and most voted to use discord instead of gitter.
Rajasegar Chandran
@rajasegar
I just made an advanced Fullscreen CLI for pnpm
https://github.com/terminal-junkies/pnpmx
Appreciate any comments and feedback.