Export a function

I need to hand off this utility to the rest of the frontend team. Export the function default so imports are simple, keep the function name sensible for stack traces, and ensure the file still exports any other helpers used by the app. Make the export last in the file and add a one-line comment above it explaining intended use.

Before I publish this module for the team, make the exported API obvious. Put the primary export at the bottom, surface the exported function name in the file top comment, and list secondary helpers together with brief one-line comments so a reviewer can grasp what they must import.

I wired an import in App.js to use calculateDiscount but the console shows cannot find module. I exported function calculateDiscount at the top as a named export, but other files expect a default. I'm worried changing the import will break customers. Should I convert calculateDiscount to a default export, change every consumer to named import, or add both export styles? Which has the least risk and what are the exact edits?

Over the last quarter we waste time swapping imports because contributors mix default and named exports across libraries. I want a habit that stops the churn: a short rule team members follow when adding exports, and a lightweight review checklist that flags mismatches. Suggest one team rule and two review checklist items that prevent this pain without blocking velocity.