On Saturday, December 14, 2013 4:33:11 AM UTC+1, Ilya Volodin wrote: > > Would you want to include a pretty big project just to be able to use a > simple JSON file? >
Exactly not. That's why I'm proposing a dedicated (but small) node module which is concerned solely with global symbols. > That seems like an overkill to me, honestly. The list of global built-ins > is pretty static and changes very rarely, so I think copy/paste is quite > justified in this case. > You may be right, although it is not completely static if you think of new runtime versions (browsers, node), or even new runtimes coming out (nashorn). Still, it feels awkward if everybody would be copying lists around, right?! > If you are concerned about maintenance, it should be pretty easy to write > a small script that would just pull the latest version from ESLint Github > account. > Yes, but would I then send pull requests to ESLint just to update the globals list? Would others do that too? And why does ESLint maintain their own and not e.g. dynamically pull in the 'vars.js' file from JSHint?! Wouldn't a stand-alone module which all could use and maintain be the best approach?! Thanks, Thomas -- You received this message because you are subscribed to the Google Groups "ESLint" 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.
