Pnpm: Meta: v1.0

[rstacruz]

Is it time we bump the version to 1.0?

[rstacruz]

v0.25 is out by the way!

https://github.com/rstacruz/pnpm/blob/master/HISTORY.md

[rstacruz]

Oh and @zkochan, send me your npm username so I can add you there as well.

[zkochan]

Great! My username on npm is the same as on github - zkochan.

[zkochan]

I am not sure v1,0 is ready. git-hosted packages installation is not ready yet.

Also I think npm link/unlink/prune/update has to be implemented as well.

[rstacruz]

re: npm access: done!

also, totally agree on those points.

[zkochan]

Out of topic, but could you please add this webhook to the project settings? https://ci.appveyor.com/api/github/webhook?id=i30tealekiaesltb

I don't have access to that. This will trigger the appveyor build. Currently I am triggering it manually.

[rstacruz]

Man GitHub really needs a chat of sorts

[rstacruz]

enabled for push, pull request and status.

[zkochan]

true story.

thanks

We can create a gitter chat by the way, It is pretty good.

[iamstarkov]

can we get support for optionalDeps in 1.0-beta?

[iamstarkov]

it used to be a problem with ava, back then when chokidar was in optionalDependencies and after pnpm install you couldnt use watch mode for tdd

[zkochan]

that should already work since v0.24.0 https://github.com/rstacruz/pnpm/pull/256

[iamstarkov]

thats so cool, @zkochan you are doing awsm job here

[zkochan]

Maybe lets update to version 1 indeed? Currently pnpm is marked as unstable or experimental just because it is pre-1. And it has less points on npms.io as a consequence.

[iamstarkov]

There are several v1 issues open left

[iamstarkov]

Like #298, #299 and #300

[iamstarkov]

Also #95 bothers me

[iamstarkov]

And let me check if it works in my office, last time pnpm didn't work with our local nexus, while npm works as expected

[iamstarkov]

I hope that npm-registry packet from #367 can solve a problem

[iamstarkov]

Also, what do you think about finishing moving to org before v1?

[zkochan]

yeah, I agree on what you're saying, lets move to an org first and fix those issues

[zkochan]

Guys, I have to tell you, I am really happy with v0.48! It is a huge improvement! This is the first version that I can use at work! Previously I always had some small issues. This one works great!

And also I had some fears regarding --preserve-symlinks and the fact that it will probably be deprecated, but with the new design it is not even needed anymore! It is used by defaulf, for now, but you can turn it off with npm config set preserve-symlinks false

I am very-very satisfied! I hope more people will discover the project and enjoy it :-)

[andreypopp]

Awesome! Will there be a lockfile before 1.0?

[zkochan]

yes, there is a lockfile already. It is called shrinkwrap.yaml. It is created automatically.

They are in beta I would say. I did not even check how they behave when deleting something

[iamstarkov]

@zkochan yay

[zkochan]

Feels like v1 is really close now. I added some points to the breaking changes issue #458.

I wonder if we need to make the breaking changes that npm5 introduced. Like linking file: dependencies and the prepare/prepublish lifecycle events

[zkochan]

I plan to release v1 on 28th of June. I'll try to finish any last breaking changes till this Sunday