The issue has been solved
A rule that examines the engine
argument of package.json
, and keeps a list of poly/ponyfills and which Node version makes them obsolete.
For instance, if you're using object-assign
, but only targeting Node 4 and higher, just use native Object.assign
. Many others.
posted by sindresorhus over 8 years ago You could almost do this entirely by examining package.json
.
Maybe there are some member functions of lodash
where you would need to scan the code, but I think package.json
gets us most of the way there.
posted by jamestalmage over 8 years agoI'd suggest keeping a list of poly/ponyfills in an external package. Might come in handy in other packages as well.
posted by SamVerschueren over 8 years agoposted by IssueHuntBot about 6 years ago @sindresorhus Can I work on this issue?
posted by doniyor2109 about 6 years ago@doniyor2109 Go ahead. Though keep in mind that this issue will require you to research what polyfills are popular and add support for those. It's a lot of work.
posted by sindresorhus about 6 years ago
I'd suggest keeping a list of poly/ponyfills in an external package. Might come in handy in other packages as well.
I agree, but I think we should just put it in eslint-plugin-unicorn
first. We can extract it later when it's more mature. That way we can iterate faster.
posted by sindresorhus about 6 years agoposted by sindresorhus about 5 years ago posted by issuehunt-oss[bot] over 1 year ago