Would you want to include a pretty big project just to be able to use a simple JSON file? 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. 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. But maybe I'm not understanding the issue correctly.
Thanks, Ilya Volodin On Friday, December 13, 2013 6:43:57 AM UTC-5, thron7 wrote: > concerns: ESLint developers > > Hi all, > > in a project I found the need to check against global symbols built into > various JavaScript runtimes (like 'Math', 'decodeURIComponent' ... all the > way to 'process' for Node and 'environment' for Rhino). > > Looking around I didn't find an NPM module that offers such lists, only > lists that are deeply integrated within specific projects, like ESLint's > conf/environments.json or JSHint's src/vars.js. > > These are very hard to re-use, and also hard to maintain outside their > specific projects. Wouldn't it make sense to extract this information into > a top-level module? What do you guys think? > > 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.
