◆ JavaScript

Transpile newer syntax

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
See the prompt↓All JavaScript tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskWe must support older browsers by Tuesday. Take the ES2022 modules I wrote and transpile them…+
We must support older browsers by Tuesday. Take the ES2022 modules I wrote and transpile them so they run in Internet Explorer 11 and recent Safari. Keep semantics the same, convert optional chaining, nullish coalescing, and class fields, and produce a single ES5 output per entry point with source maps. Run the project’s tests and report any syntax features that need manual polyfills.
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 deliver the transpiled bundle to QA, make the output readable enough to verify…+
Before I deliver the transpiled bundle to QA, make the output readable enough to verify behavior. Highlight where modern features were transformed, annotate places that required helpers or polyfills, and recommend which polyfills are necessary at runtime versus which need feature-detection. Flag any transforms that could degrade performance in older browsers.
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 CI shows all tests passing after transpilation, yet customers on older Android browsers see…+
Automated tests pass but production users on older phones fail
My CI shows all tests passing after transpilation, yet customers on older Android browsers see blank screens. I suspect a missing polyfill or a transformed module loader issue. I don’t know which feature is missing in the field and cannot reproduce the exact environment. What should I check first and what quick diagnostic can I add to capture the failing feature on the client?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternEvery release we forget to include a small polyfill and only discover it from customer reports.…+
We repeatedly forget required polyfills for target browsers
Every release we forget to include a small polyfill and only discover it from customer reports. It costs us hotfixes and credibility. What workflow change or checklist will reliably catch missing polyfills before release without adding huge bundle weight?
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.