GitHub Bounties💵 paid workby mvmax-devscored by google/gemini-2.5-flash

SecureBananaLabs/bug-bounty: @freelanceflow/ui package entrypoint should be directly importable (reissue via #743)

Visit project ↗Discussion ↗

💵 Funded work— see “Deliver it” below for how to respond.

Opportunity

AI-buildable

Traction

Creativity

The take

effort: ~weekend

This bounty involves fixing an ESM import issue in a JavaScript/TypeScript UI package within a monorepo. The core problem is that the package's `main` entry point points to a TypeScript source file, and its components are not properly exported as compiled JavaScript for direct consumption by Node.js ESM clients. The task requires configuring the build process to emit valid JavaScript entrypoints and TypeScript declarations.

Demand & gap

Painkillerdemand 79

Demand

Will. to pay

Gap

Buyer

Developers

The gap in what exists: There's a clear, funded need for a developer to fix a specific package export issue, which is a common pain point in modern JavaScript development.
Wedge to win: Solve the problem directly as a paid contractor/bounty hunter for SecureBananaLabs, leveraging expertise in TypeScript/Node.js package publishing.
Reputation value (worth doing free for proof) — 60/100: Successfully completing a public bounty for a named organization, even on a specific bug, serves as strong proof of technical competency for future developer-focused freelance or product work.
Likely monetization: bounty payment

Deliver it

A starter prompt for Claude Code, what you'll need, and how to reach them.

You are an expert TypeScript/Node.js developer. The goal is to fix a package entrypoint issue in a monorepo. I need you to address issue #2787 in the `SecureBananaLabs/bug-bounty` repository, specifically for the `@freelanceflow/ui` package. The problem is that `main` points to `src/index.ts` and components like `./Button` and `./Card` are re-exported from it without emitted JavaScript entrypoints, causing Node.js ESM consumers to fail. Your task is to modify the package's build configuration to correctly compile TypeScript to JavaScript, generate declaration files, and ensure the `package.json` `main`, `module`, and `types` fields correctly point to the compiled output, enabling direct ESM imports from Node.js. Focus on using `tsup` or `rollup` as the bundler if not already present, ensuring proper `exports` map in `package.json` if needed. Provide the necessary code changes, build script updates, and a detailed explanation of the fix. The final deliverable must pass the test `node -e "import('@freelanceflow/ui')"` without errors. Use Next.js 16 App Router, React 19, Tailwind v4 as the conceptual framework for general web components, though the specific fix is for a generic JS package.

Prerequisites — cost & what to learn

How you'd build it

1Fork the SecureBananaLabs/bug-bounty repository.
2Locate the `@freelanceflow/ui` package within the monorepo structure.
3Analyze the existing `package.json` and build scripts (e.g., `rollup`, `tsup`, `esbuild`, `tsc`) for the `@freelanceflow/ui` package.
4Modify the build configuration to correctly compile TypeScript to JavaScript, emit declaration files, and ensure the `package.json` `main`, `module`, and `types` fields point to the correct emitted files (e.g., `dist/index.js`, `dist/index.mjs`, `dist/index.d.ts`).
5Add a post-build step or configure the bundler to create proper re-exports for `./Button` and `./Card` from the compiled JavaScript.
6Verify the fix by running the provided `node -e "import('@freelanceflow/ui')"` command and ensuring it no longer errors, and that components can be imported and used.

Risks & moats

Navigating an unfamiliar monorepo setup and build tooling could take longer than expected.
Ensuring compatibility with existing build steps and other packages in the monorepo could introduce unforeseen complexities.
The fix might require specific knowledge of TypeScript's `moduleResolution` and `exports` maps in `package.json` for complex scenarios.
The issue is limited to the original author, meaning the operator cannot directly claim this specific bounty, but would need to create a similar issue (which is explicitly allowed by the prompt).

Original context

Bounty (amount on the issue). ## Bug The `@freelanceflow/ui` workspace package currently declares `main` as `src/index.ts`, and that file re-exports `./Button` and `./Card` without emitted JavaScript entrypoints. This makes the package fail when imported directly by a Node/ESM consumer from the workspace: ```sh node -e "import('@freelanceflow/ui')" ``` It currently errors because the package entrypoint points at TypeScript source and the component modules are not resolvable as runtime JavaScript. The package should expose a real JavaScript entrypoint while preserving TypeScript declarations for consumers. --- This issue is limited only to the creator of this issue. This means that only the issue author can attempt to solve this issue. If you would like to work on it, please create another issue with the same contents and refer to issue #743 for more information. Parent bounty: #743