◆ JavaScript

Configure bundler build

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskWe need a reproducible production build today. Configure the bundler so it produces a single…+
We need a reproducible production build today. Configure the bundler so it produces a single production bundle per entry with deterministic filenames, includes hashed assets for caching, generates source maps, performs tree shaking, and fails the build on unresolved imports. Document the exact build command our CI will run and the output paths for deployment.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore I hand the bundler config to operations, make it easier for a reviewer to validate. Show…+
Before I hand the bundler config to operations, make it easier for a reviewer to validate. Show where vendor code is split from app code, surface the largest modules and why they aren’t tree-shaken, list the file name patterns and cache headers we should use, and point out any long-running plugins that slow CI.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentMy local production bundle is 1.2 MB but CI produces a 2.8 MB bundle with identical source.…+
CI artifacts differ from my local build
My local production bundle is 1.2 MB but CI produces a 2.8 MB bundle with identical source. Deployments started failing because cache headers changed. I suspect a missing plugin or different node resolution in CI. I don’t know what exact config divergence to look for. What are the most likely causes and the precise checks to run to pinpoint the difference quickly?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternEvery project lands its own slightly different bundler config and we lose time debugging subtle…+
Config drifts across projects and teams
Every project lands its own slightly different bundler config and we lose time debugging subtle differences across teams. Builds behave differently in staging and prod and on developers’ machines. What consolidation or habits should we adopt so configs are consistent, easy to audit, and faster to update across repositories?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from JavaScript's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.