Skip to content

Conversation

@ryanleecode
Copy link

Currently every package is outputting CJS. This adds support for ESM and CJS output for the https-proxy-agent package. if accepted, this approach can be used for other packages.

@changeset-bot
Copy link

changeset-bot bot commented Jun 2, 2025

🦋 Changeset detected

Latest commit: 561d666

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
https-proxy-agent Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@vercel
Copy link

vercel bot commented Jun 2, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
proxy-agents ✅ Ready (Inspect) Visit Preview Jun 3, 2025 0:04am

@ryanleecode ryanleecode force-pushed the feat/https-proxy-agent-esm branch from 3cc2f30 to df64535 Compare June 2, 2025 23:42
@ryanleecode ryanleecode changed the title feat: add esm support to https-proxy-agent feat(https-proxy-agent): add esm support to https-proxy-agent Jun 2, 2025
@TooTallNate
Copy link
Owner

Curious - what is the issue with CJS?

@ryanleecode
Copy link
Author

ryanleecode commented Jul 7, 2025 via email

@TooTallNate
Copy link
Owner

Not sure what you mean. As in await import('https-proxy-agent')? Or can you show me code that doesn't work?

@bashmish
Copy link

Curious - what is the issue with CJS?

I'm migrating my package to ESM and wanna be able to just import it in the ESM context like so

import { HttpsProxyAgent } from 'https-proxy-agent';

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants