Architecture scenarioMedium~10 minJavaScript Language & Async Semantics / 8 of 9

Interview question

How would you structure JavaScript module boundaries so code remains reusable and unused code can be removed safely?

Designs explicit ESM boundaries with focused exports, controlled side effects, and dependency direction that supports safe bundling.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

I organize modules around cohesive responsibilities and expose a small public API with static ESM imports and exports. I keep initialization side effects separate from reusable definitions, because bundlers can remove unused exports only when they can analyze the graph safely. Consumers should depend on the public boundary rather than reaching into internal files.

Full answer below

Practice focus

Judgment about public module contracts, side effects, circular dependencies, and the limits of tree shaking.

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Overview
Tree shaking is a build optimization, not an architectural guarantee. Clear static module boundaries make both reuse and analysis easier.
I organize modules around cohesive responsibilities and expose a small public API with static ESM imports and exports. I keep initialization side effects separate from reusable definitions, because bundlers can remove unused exports only when they can analyze the graph safely. Consumers should depend on the public boundary rather than reaching into internal files.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
A feature package might export its component, contract, and factory from one intentional entry point while keeping adapters internal. I avoid a giant barrel that accidentally imports every feature or creates circular dependencies. I verify the production bundle because dynamic imports, CommonJS interop, package side-effect declarations, and re-export patterns can change what the tool can eliminate.
Finish
Advanced answer
Optional deeper angle for production judgment and nuance.
I treat bundle size as one outcome, not the sole design goal. Excessive micro-modules and unstable deep imports can make ownership worse even if a demo tree-shakes. I enforce dependency direction, split optional features at user-relevant boundaries, and monitor chunk composition over time. Package metadata must describe side effects truthfully; marking an effectful module as side-effect free can remove required initialization and create a production-only defect.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Assuming unused source text is always removed automatically.
Putting registration or global mutation inside widely imported modules.
Using broad barrel files without checking their dependency graph.
Publishing internal file paths as an unofficial public API.

Red flagsCandidateRed flagsSignals that an interviewer may treat as risky.Open details

Details

The design relies on incorrect side-effect metadata.
Circular dependencies determine initialization order.
Bundle claims are made without inspecting the production output.

Follow-up prompts

Quick interviewer prompts inside this drill.

Follow-up questionsCandidateFollow-up questionsLikely next questions after the main answer.Open details

Details

Treat these as the next interviewer turn. Answer one out loud, then save the gap in your practice notes.

What makes a module difficult to tree-shake?
When would you use a dynamic import?
Why can a barrel file become problematic?

Continue the section

Next in JavaScript Language & Async Semantics: Equality and coercion

Step 9 of 9

Which JavaScript equality and coercion rules matter in application code, and how do you avoid surprising comparisons?

Practice route

Read core answer Review checklist Follow-up prompts Track progress

Finished this drill?

Practice freely. Sign in only when you want to save completion, confidence, notes, or bookmarks.

New to Aporeon? Create account

Drill details

Human editorial direction

Aporeon is shaped by Aleksandar Tomovski, a software developer with experience on both sides of technical interviews. Content is reviewed for accuracy, natural spoken delivery, useful depth, and honest trade-offs.

About the creator Editorial standards

Was this drill useful?