News for hackers. Stuff that matters.

blubbi2

Re:Yarn – A new package manager for JavaScript on Tuesday October 11, 2016 @11:17PM (#12690220)
That's not 100 % accurate. Arguably symlinks are kinda weird under Windows, but that doesn't mean symlinking node_modules doesn't work (you just need admin privileges).

(Disclaimer: I'm the author of ied.)

Re:Yarn – A new package manager for JavaScript on Tuesday October 11, 2016 @02:02PM (#12686875)
> We initially used a method similar to ied when we first started experimenting with internal usage at Facebook.

Would be really nice if you would e.g. add ied to "Prior art" on your README then. ;)

/ @alexanderGugel (the guy behind ied)

Re:Maintainable JavaScript (2014) on Saturday July 16, 2016 @06:25AM (#12105874)
Probably easier to just use an assertion library here. E.g.

  assert.ok(element)
Re:Show HN: ied – an alternative package manager for Node on Tuesday November 17, 2015 @08:26AM (#10580843)
Yup. Thanks.
Re:Show HN: ied – an alternative package manager for Node on Monday November 16, 2015 @06:27PM (#10578106)
They are extremely different.

I made a quick comparison here: https://gist.github.com/alexanderGugel/a10ed5655d366875a280

Basically ied uses symlinks in order to resolve circular dependencies, while ied exploits the fact that require "falls back" in the directory structure.

Re:Show HN: ied – an alternative package manager for Node on Sunday November 15, 2015 @08:16PM (#10572080)
Agreed. It's definitely on the roadmap. Should be done in a couple of weeks.
Re:Show HN: ied – an alternative package manager for Node on Sunday November 15, 2015 @07:09PM (#10571845)
Awesome! Glad it worked that well! Please let me know if you run into any bugs: https://github.com/alexanderGugel/ied
Re:Show HN: ied – an alternative package manager for Node on Sunday November 15, 2015 @06:49PM (#10571797)
Great to hear that! shrinkwraps + rollbacks are definitely coming!
Re:Show HN: ied – an alternative package manager for Node on Sunday November 15, 2015 @06:48PM (#10571792)
Although using ied and npm at the same time for installing dependencies should work, you might run into some weird corner cases.

Therefore, npm and ied are compatible in the sense that you can use ied to install packages and npm for publishing them. At least that's the level of compatibility that is currently supported.

shrinkwrap is definitely coming :)

Re:Show HN: ied – an alternative package manager for Node on Sunday November 15, 2015 @06:33PM (#10571748)
Its install process is very different from the one npm uses. E.g. just look into the node_modules directory produced by npm vs the one produced by ied.

Also the way it wires up dependencies (using symlinks) has been called "non humane design" by npm... so I thought it would be easier to just start a new project... it's not a lot of code/logic needed there actually... :)

Re:Show HN: ied – an alternative package manager for Node on Sunday November 15, 2015 @05:48PM (#10571592)
Already taken by Atom's package manager: https://github.com/atom/apm
Re:Show HN: ied – an alternative package manager for Node on Sunday November 15, 2015 @05:09PM (#10571446)
The initial set of dependencies is being installed via npm, the it installs its own dependencies via ied if told so: https://github.com/alexanderGugel/ied#installation

This is a "cool" feature during development, since it's a nice proof of concept.

Originally I checked in the node_modules directory, but then reddit was shitting on me as usual (yes, you shouldn't check in node_modules in an actual app, but this is PACKAGE MANAGER!). As far as I know, npm has also its own dependencies check in + a ton of packages as tarballs for tests, so I might do that later.

Re:Show HN: ied – an alternative package manager for Node on Sunday November 15, 2015 @05:05PM (#10571427)
Mostly, yes, but there are some features that are still missing:

`ied publish` and `ied version` is coming next week. I'm also thinking of adding scoped modules, but I'm not sure about that yet.

You can also configure a private npm registry to be used: https://github.com/alexanderGugel/ied/blob/master/lib/config...

Re:Show HN: ied – an alternative package manager for Node on Sunday November 15, 2015 @04:32PM (#10571306)
As I said earlier, it wasn't my intention to name it after a weapon.

That being said, it's a three letter name. It's very unlikely NOT to run into naming conflicts here.

edge - taken by Microsoft

jpm - JPMorgan

ppm - taken by Perl package manager: https://en.wikipedia.org/wiki/Perl_package_manager

fpm - taken by Effing package management: https://github.com/jordansissel/fpm

bpm - beats per minute

ayp - terrible to type, although taken by "Adequate Yearly Progress": https://en.wikipedia.org/wiki/Adequate_Yearly_Progress

nnm - What happens when it's no longer new?

Just in Germany for example there are a ton of companies called ISIS (just google "ISIS GmbH"). Being offended by a three letter shell command seems a bit over the top to me to be honest.

Edit: I won't respond to further comments on the naming issue. It wasn't my intention to name it after a weapon. As I said earlier, I will change the name as soon as anyone proposes a better one.

Re:Show HN: ied – an alternative package manager for Node on Sunday November 15, 2015 @04:00PM (#10571186)
This looks very interesting!

Also related: https://github.com/dominictarr/npmd

Re:Show HN: ied – an alternative package manager for Node on Sunday November 15, 2015 @03:52PM (#10571136)
Damn. Didn't think of that.

In fact I literally just renamed it: https://github.com/alexanderGugel/ied/commit/84628b3c871c85d...

Originally it was called mpm, but I figured that would have been pretty confusing, but it looks like the new name isn't necessarily better.

I'm pretty terrible at naming. Any suggestions are more than welcome!

Re:Show HN: ied – an alternative package manager for Node on Sunday November 15, 2015 @03:49PM (#10571122)
Hey everyone!

I made this. I'm happy to answer any questions, but please bear in mind that this is a WIP. There is still a lot of work to be done, although feature parity with npm is not the goal.

Upcoming features are:

* Nix-like rollbacks * built in registry server * discovery + installation via BitTorrent DHT

Would love to get any feedback!

Older »