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

Description

#!/usr/bin/env node

export const foo = {};

export {}

#!/usr/bin/env node

console.log('foo');

Contributor guide

Tech stack

javascript

Domain

toolingdeveloper experience

Issue type

feature

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

3

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

1-3 hours

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

fresh

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

clear

Prerequisites

understanding of ESLint rulesfamiliarity with AST

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

50

Research direction

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'.