fixes #5

[heapwolf]

a quick fix for ensuring that the release downloaded is the latest.

[max-mapper]

@hij1nx this is really cool!

my only concern is that getting the latest version every time is essentially doing atom-shell: '*' in dependencies, which makes things non-deterministic by default.

what do you think about making this opt-in, e.g. if you do ATOM_VERSION=latest npm install atom-shell it gets the latest version, otherwise it gets the version specified in the source code?

[heapwolf]

That seems like a valid concern from one perspective. I was under the impression though that this was more of a dev tool than a dependency, so is allowing * really a problem (especially considering how unstable atom shell is and how each release is basically a bunch of bug fixes)?

[max-mapper]

IMO even if it's a devDependency it should still get versioned. It avoids a problem where the code worked when you wrote it and then 6 months later someone tries to get it to run and it breaks

[heapwolf]

Well, it's hard to ague that because I agree. What If it defaults to a version but uses a flag to pull latest?

[max-mapper]

+1 that seems like a good solution

[jprichardson]

Yeah, love this proposal. @mafintosh thoughts?

[mafintosh]

I'm all for this. Sorry for being slow. @hij1nx could you resolve the conflict so I can merge this? :)

[sindresorhus]

var arch = platform === 'win32' ? 'ia32' : os.arch()

[heapwolf]

platform is always a string, so === is pointless. parens for readability.

[sindresorhus]

Would also be nice if you could give this pull request a descriptive title.

[heapwolf]

lol, just realized this is a dead PR anyway. ffs.