My thoughts on the matter are articulated in the issue linked in the
OP. Also everything that Ben has written in this thread is 100%
correct.
Furthermore:
We only remove/break deprecated APIs if they're in the way. If it's
buried in a locked module, then that's highly unlikely. (Someone
would have to find an extremely severe bug that could only be fixed by
removing require.extensions.)
However, we also aren't likely to *fix* any issues that you have with
that deprecated API. That's the issue that started this round of
require.extensions discussion. The only change that we'd make to it
is to remove it or add a deprecation warning, and we won't be doing
that, since there's no reason to.
In the near future, the module rating system that we're building will
penalize any module that uses deprecated APIs. It will be ranked
lower in searches, have a smaller score next to its name, and perhaps
even print a warning when it is installed by npm.
If you would like to ensure that your program is not doing anything
stupid, you can use the `node-strict` module, and add
`require('node-strict')` to your main file. It's still a work in
progress, but it prevents require.extensions and other poor choices.
On Sat, May 11, 2013 at 7:00 PM, Bruno Jouhier <[email protected]> wrote:
> Cool cause I need this to work forever: https://github.com/bjouhier/node-lol
>
> OTHERWIZ DAZ NO FUN!
>
> Sorry for my lolcat, it's a bit weak.
>
> Bruno
>
> On Sunday, May 12, 2013 1:56:23 AM UTC+2, Ben Noordhuis wrote:
>>
>> On Sat, May 11, 2013 at 9:05 AM, ~flow <[email protected]> wrote:
>> > what conventions / best practices / techniques can we come up that will
>> > allow us to 'publish in my language, run as javascript' the day that
>> > require.extensions is gone?
>>
>> What seems to be getting lost in this discussion is that
>> require.extensions is not actually going away, certainly not in the
>> near future and probably never.
>>
>> Deprecation in API-locked parts of node.js core means "you really
>> shouldn't use this", not "we'll remove it whenever the fancy strikes
>> us."
>
> --
> --
> Job Board: http://jobs.nodejs.org/
> Posting guidelines:
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To post to this group, send email to [email protected]
> To unsubscribe from this group, send email to
> [email protected]
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "nodejs" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
---
You received this message because you are subscribed to the Google Groups
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
