es-modules
/es-modules
Use when reviewing scripts, client components, bundles, or runtime behavior related to Use ES modules (import/export). Inspect both source code and the browser execution path so fixes target the real bottleneck or bug.
- Author
- thedaviddias ↗
- Repository
- front-end-checklist ↗
- Licence
- MIT
- Last repository change
- 06.10.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 2
No signals detected. Repository changed on 06.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when reviewing scripts, client components, bundles, or runtime behavior related to Use ES modules (import/export). Inspect both source code and the browser execution path so fixes target the real bottleneck or bug.
Original author description
Use when reviewing scripts, client components, bundles, or runtime behavior related to Use ES modules (import/export). Inspect both source code and the browser execution path so fixes target the real bottleneck or bug.
How it works
- Quick Reference
- Check
- Fix
- Explain
- Code Review
SKILL.md preview
--- name: es-modules description: "Use when reviewing scripts, client components, bundles, or runtime behavior related to Use ES modules (import/export). Inspect both source code and the browser execution path so fixes target the real bottleneck or bug." metadata: category: javascript priority: high difficulty: beginner estimatedTime: "15" source: frontendchecklist.io url: https://frontendchecklist.io/rules/javascript/es-modules --- # Use ES modules (import/export) ES modules are statically analyzable — bundlers can determine at build time what code is actually used and eliminate the rest (tree-shaking). CommonJS require() is dynamic and prevents this optimization. ES modules are also the browser-native standard, reducing the need for build-time transformation. ## Quick Reference - Use import/export syntax instead of require()/module.exports - Named exports improve IDE autocompletion and enable tree-shaking - Add type="module" to script tags or use a bundler to load ES modules in browsers - Default exports are fine but named exports scale better in large codebases ## Check Identify any use of require(), module.exports, or exports in this JavaScript file that should be converted to ES module syntax. ## Fix Convert all require() and module.exports statements to ES module import/export syntax. ## Explain Explain the benefits of ES modules over CommonJS, including tree-shaking, static analysis, and browser support. ## Code Review Review scripts, client components, and browser execution paths related to Use ES modules (import/export). Flag exact imports, event handlers, runtime side effects, or blocking operations that violate the rule, and state how the change should be verified in the browser. --- For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`. Rule page: https://frontendchecklist.io/rules/javascript/es-modules
Files in this package (2)
- SKILL.md 2 KB
- references/rule.md 3 KB
Versions
The database has no other skills named es-modules.
Database snapshot: 13.11.2026 · package version ad2dfdd15b79 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100error-handling
Use when reviewing scripts, client components, bundles, or runtime behavior related to Implement proper error handling. Inspect both source code and the browser execution path so fixes target the real bottleneck or bug. - 100json-safety
Use when reviewing scripts, client components, bundles, or runtime behavior related to Parse JSON safely with error handling. Inspect both source code and the browser execution path so fixes target the real bottleneck or bug. - 90Workflow Runtime Debug
Debug workflow runtime behavior and test frontend features using the nc MCP bridge. Use when debugging workflow execution, testing UI components, inspecting DOM/state, writing frontend tests, or when user mentions nc_eval, nc_run_test, nc bridge, __workflowTest, test harness, or runtime debugging. - 95organize-modules
Apply private modules with public re-exports (barrel export) pattern for clean API design. Includes conditional visibility for docs and tests. Use when creating modules, organizing mod.rs files, or before creating commits. - 100module
What a LangWatch module is and how to start one: the four packages (contract, process, browser, client), modules/catalogue.json, pnpm generate:modules, the specs/ and adrs/ folders, the dependency direction between halves, and what another module may import. Use when someone… - 100source-code-context
Use when Hermes is integrating a package, SDK, API client, framework, or open-source tool and should inspect real local source instead of guessing API names or behavior from stale docs.