Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 20:40

    zkochan on main

    fix(build-modules): fix incorre… (compare)

  • 20:40
    zkochan closed #3369
  • 20:13
    zkochan commented #2848
  • 19:56
    thynson synchronize #3369
  • 19:55
    thynson commented #3369
  • 19:48
    zkochan commented #3369
  • 18:58
    thynson commented #3369
  • 18:55
    thynson edited #3369
  • 18:54
    thynson review_requested #3369
  • 18:54
    thynson opened #3369
  • 17:45
    javier-garcia-meteologica review_requested #3368
  • 17:45
    javier-garcia-meteologica opened #3368
  • 16:17
    SanketD92 commented #2848
  • 16:10
    SanketD92 commented #2848
  • 16:10
    SanketD92 commented #2848
  • 15:44
    j3rem1e commented #3360
  • 06:40
    YogliB edited #3326
  • 06:39
    YogliB commented #3326
  • 06:38
    YogliB edited #3326
  • 06:36
    YogliB edited #3326
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.
geekyi
@geekyi
Okay, the project I used had an npm command in the package.json script:. I replaced it with pnpm equivalents, but not before I accidentally ran npm.
Any pointers how to 'unpolute" nodemodules now?
1 reply
st-clair-clarke
@st-clair-clarke
Hi fellows. I am new to pnpm. I installed it and ran my nrwl nx application. The app runs and opens, but my UIs are messed up - staggered and not seeing what I normally see. I am using Linux Mint v20. Has anyone seen this before? And how to I correct it. My app ran fine with npm. Thanks.
matrixbot
@matrixbot

Synth > <@gitter_zkochan:matrix.org> using discord is not obligatory. If someone doesn't want to use it, just use Github issues.

Not strictly true. Using Discord is a lot easier for support, as it's a direct chat. Not really the same on Matrix.

Synth Would you consider setting up a Matrix bridge? It takes 5 seconds, and it's all on t2bot.io
3 replies
hinell
@hinell
Filed an an issue on deprecating pnpm-workspace.yaml, please checkout and get involved: pnpm/pnpm#2966
Antonio Mayrinck Moura
@nthypes

Folks, it's possible to ignore a pnpm-lock.yaml when it exists?

pnpm i --filter . --link-workspace-packages false seems to install from workspace even with the flag because of the pnpm-lock.yaml

Eldar
@Eldar-X
Hi! i have an issue with monorepo :( In my project 1 project is vue based and in other i have plugin for this project but type augmentation not working because when vue project symlink plugin there is also node_modules dir inside of symlinked plugin and typescript can't resolve this is a same type. When i remove node_modules from my plugin everything working but it's force me to install and remove node modules every time
Vaughan Rouesnel
@vjpr

@zkochan What is themy-project/node_modules/.pnpm/node_modules dir? Some dependencies are sitting there which erroneously get found.

I found it to be the cause behind this issue (facebook/react-native#29301). Metro bundler creates worker child processes…and when these processes resolve their dependencies they do it relative to their file location in node_modules…which then means that when searching upwards for their dependencies they hit .pnpm/node_modules/metro which is the wrong version. How does this version get chosen?

There is also a version of React there…which seems odd because its implying a fallback but shouldnt pnpm be strict about deps?

Maybe a bad public-hoist-pattern? What does "By default, all packages are hoisted” mean in hoist-pattern docs…is this to .pnpm/node_modules or to .pnpm/foo|bar|baz...

Question: how does the version to be hoisted get chosen?
I'm guessing my issue comes from an u declared peer dependency of jest-worker
Jonathan Stewmon
@jstewmon

:wave: Hi, I'm trying to get started with pnpm (5.13.5) in a monorepo which contains a create-react-app package...

With the default settings, react-scripts precheck fails because it can find an ancestral package with a different version than the one it wants. I could just ignore the preflight check, but I expected to be able to use either the pnp linker or hoist=false to ensure that my react app package does not see any ancestral node_modules.

When I use node-linker=pnp and symlink=false, react-scripts build fails with Couldn't find the package to use as resolution source thrown by pnp-webpack-plugin, which I suppose is because pnp-webpack-plugin is searching upward from its location in the virtual store of my repo root.

When I use hoist=false, all of my packages' direct dependencies have empty node_modules directories (except for the .bin directory). This is most unexpected, as I thought the description of hoist=false indicated that the node_modules directories of all packages would contain directories of exactly the packages mentioned in the dependencies property of their package.json.

TIA for clarifying anything I've misunderstood or tips on how to overcome these issues. :pray:

Jonathan Stewmon
@jstewmon
Doh, just noticed the deprecation link in the title... cross-posting my question on Discord...
Günter Zöchbauer
@zoechi

I just started with pnpm
When running pnpm i I get

pnpm i
 WARN  Moving @angular-devkit/build-angular that was installed by a different package manager to "node_modules/.ignored
 WARN  Moving @angular/cli that was installed by a different package manager to "node_modules/.ignored
 WARN  Moving @angular/compiler-cli that was installed by a different package manager to "node_modules/.ignored
 WARN  Moving @angular/language-service that was installed by a different package manager to "node_modules/.ignored
 WARN  Moving @nrwl/cli that was installed by a different package manager to "node_modules/.ignored

Can these folders be deleted?
Why are they created?

LeoDog896
@LeoDog896
basedir=$(dirname "$(echo "$0" | sed -e 's,\,/,g')")
I'm getting this error when using pnpm run start on my script. I'm using sapper
st-clair-clarke
@st-clair-clarke
I would suggest that posting be done on Discord. It seems far more active than here!
Sunny
@xrsunny_gitlab
Is there a pnpm init command or will it do with npm init
Hmmm just typed in pnpm init to find that the init command actually exists (:
Brendon John Muschamp
@brendonjohn

:wave: Hey ya'll, I've been reading through the docs and are trying to find:

  • Can I specify a minimum pnpm version required for a project?

I haven't seen this in the doc, I'm wondering how others have solved this?

QP
@theqp
@brendonjohn the channel description is:
pnpm/pnpm
DEPRECATED -- USE DISCORD --> https://bit.ly/pnpm-discord-invite
1 reply
Imad DJEBARNI
@ims16_gitlab
Hello everyone, I'm actually migrating my angular project from NPM to PNPM and I'm facing a style issue, if someone can give me some help please! ERROR in multi ./src/styles/import.scss ./node_modules/primeng/resources/primeng.min.css ./node_modules/primeicons/primeicons.css ./node_modules/font-awesome/css/font-awesome.min.css ./node_modules/flag-icon-css/css/flag-icon.min.c ss ./node_modules/ion-rangeslider/css/ion.rangeSlider.css ./src/styles/ion.rangeSlider.skinFlat.css ./node_modules/angular2-multiselect-dropdown/themes/default.theme.css ./node_modules/@angular/material/prebuilt-themes/indigo-pink. css ./src/styles/index.scss Module not found: Error: Can't resolve 'E:\Dev\UVIE\uvie-front\src\styles\ion.rangeSlider.skinFlat.css' in 'E:\Dev\UVIE\uvie-front'
1 reply
Stronger
@x-strong
Hi everyone, I'm using pnpm to install packages for angular project, and after installing packages I saw that there is a .pnpm folder in the node_module directory, all packages are placed into the .pnpm folder, this cause a problem that ts could not found any module. Did anybody encountered this problem? and what should I do to solve it?
image.png
dog-single
@SallyOne
image.png
image.png
hello,in docker use pnpm install dep, will report 404.
WARN  GET https://registry.npmjs.org/arr-flatten/download/arr-flatten-1.1.0.tgz error (ERR_PNPM_FETCH_404). Will retry in 1 minute. 1 retries left.  WARN  GET https://registry.npmjs.org/anymatch/download/anymatch-1.3.2.tgz error (ERR_PNPM_FETCH_404). Will retry in 1 minute. 1 retries left.  WARN  GET https://registry.npmjs.org/micromatch/download/micromatch-2.3.11.tgz error (ERR_PNPM_FETCH_404). Will retry in 1 minute. 1 retries left.  WARN  GET https://registry.npmjs.org/arr-diff/download/arr-diff-2.0.0.tgz error (ERR_PNPM_FETCH_404). Will retry in 1 minute. 1 retries left.  WARN  GET https://registry.npmjs.org/chokidar/download/chokidar-1.7.0.tgz?cache=0&sync_timestamp=1610773765549&other_urls=https%3A%2F%2Fregistry.npm.taobao.org%2Fchokidar%2Fdownload%2Fchokidar-1.7.0.tgz error (ERR_PNPM_FETCH_404). Will retry in 1 minute. 1 retries left.  ERROR  GET https://registry.npmjs.org/bowser/download/bowser-1.9.4.tgz: Not Found - 404 No authorization header was set for the request.
2 replies
Rohit Verma
@rverma-nsl
hi all, need some help in enabling rush in an existing pnmp workspace folder. The dependency handling of rush is acting different when coming from vanilla pnpm. In our current project we are getting these kind of exceptions The package "@aws-cdk/iam" cannot be listed in both "dependencies" and "peerDependencies". Any idea how to fix ?
John Winston
@winston0410
Hi, has anyone tried docker-compose with a pnpm monorepo before? Is this a good idea to start in the first place? Instead of creating multiple separate images, it will create a big single image, and I am not sure if this is a good thing