For what it's worth, new packages in npm are no longer allowed to have
upper case characters in the name, and haven't been for a while.
(Existing mixed-case packages are unaffected, and can still get
updates.)
On Thu, Jun 28, 2012 at 7:06 PM, Brian <theturtl...@gmail.com> wrote:
> I've had this issue bite me as well on OS X. Everything was working
> fine on my development platform, and then when I pushed to production
> it wouldn't start up, so I had about 5 minutes of downtime while I
> scrambled to figure out what went wrong, check in the fix to Github,
> and redeploy.
>
> Brian
>
>
> On Thu, Jun 28, 2012 at 2:28 PM, Kris Kowal <kris.ko...@cixar.com> wrote:
>> For what it’s worth, this hazard is not unique to Windows. A lot of us
>> are working on OS X.
>>
>> This is probably surprising to a lot of folks. OS X by default also
>> ships with a case-insensitive file system.
>>
>> $ touch Foo.txt
>> $ ls foo.txt
>> foo.txt
>>
>> It is alas too late to restrict module identifiers to lower-case (per
>> CommonJS) by throwing exceptions for ids that include upper-case
>> letters. Consider:
>>
>> require("../build/Release/context.node");
>>
>> Safely making module identifiers case-sensitive would amount verifying
>> that the canonical/realpath of the identifier matches the requested
>> identifier.
>>
>> Kris Kowal
