Rule proposal: `no-exports-in-scripts`

描述

#!/usr/bin/env node

export const foo = {};

export {}

#!/usr/bin/env node

console.log('foo');

贡献者指南

技术栈

javascript

领域

toolingdeveloper experience

议题类型

feature

难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。

3

预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。

1-3 hours

活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。

fresh

清晰度议题是否清楚说明期望改动、验收标准和下一步。

clear

前置要求

understanding of ESLint rulesfamiliarity with AST

新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。

50

研究方向

First, read ESLint's official documentation on creating custom rules (https://eslint.org/docs/latest/extend/custom rules). Then explore the existing rules in this repository under 'rules/' to understand the pattern and used utilities like 'createRule' from '../../utils/'. Implement the rule by adding a new file in 'rules/no exports in scripts.js' and its test in 'test/snapshots/no exports in scripts.js.md'. Ensure the rule detects export statements inside files that start with a shebang (#!). Finally, run the test suite with 'npm test'.