Rule proposal: Don't import util Node.js core module directly

[sindresorhus]

This module is the perfect case for using destructuring / named imports, as it's just a bunch of unrelated functions.

Fail

const util = require('util');

import util from 'util';

import * as util from 'util';

Pass

const {promisify} = require('util');

import {promisify} from 'util';

---

IssueHunt Summary

futpib has been rewarded.

Backers (Total: $60.00)

• issuehunt ($60.00)

Submitted pull Requests

• #232 #211 - Add no-direct-import rule
• #789 Add import-style rule

---

Tips

• Checkout the Issuehunt explorer to discover more funded issues.
• Need some help from other developers? Add your repositories on IssueHunt to raise funds.

[IssueHuntBot]

@issuehuntfest has funded $60.00 to this issue. See it on IssueHunt

[futpib]

Instead of being utils-specific why not make it accept a set of modules as an option (with utils being among defaults)?

[sindresorhus]

Good idea! Let’s do that. We could add lodash and underscore to the default list too. Maybe we could also have a list for the inverse? For example, chalk should not be destructured, but people still do. Same with the core path module.

[arshadkazmi42]

@sindresorhus I would like to work on this.
Can you provide some more details what is the finalize approach for this?

[sindresorhus]

If anyone wants to work on this, see the previous attempt and feedback: #232

[issuehunt-oss]

@sindresorhus has rewarded $54.00 to @futpib. See it on IssueHunt

• 💰 Total deposit: $60.00
• 🎉 Repository reward(0%): $0.00
• 🔧 Service fee(10%): $6.00