Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Modernize @rollup/plugin-terser to module #1659

Closed
wants to merge 1 commit into from

Conversation

vdegenne
Copy link

Rollup Plugin Name: @rollup/plugin-terser

This PR contains:

  • bugfix
  • feature
  • refactor
  • documentation
  • other

Are tests included?

  • yes (bugfixes and features will not be merged without tests)
  • no

Breaking Changes?

  • yes (breaking changes will not be merged unless absolutely necessary)
  • no

If yes, then include "BREAKING CHANGES:" in the first commit message body, followed by a description of what is breaking.

List any relevant issue numbers:

Description

@tada5hi
Copy link
Member

tada5hi commented Dec 30, 2023

I would like to postpone this until we migrate the whole monorepo to esm.

@tada5hi tada5hi closed this Dec 30, 2023
@shellscape shellscape reopened this Dec 30, 2023
@shellscape
Copy link
Collaborator

Let's not close PRs until we've had a chance to review.

@shellscape
Copy link
Collaborator

@vdegenne could you please explain your reasons for this change? We export both ESM and CJS for each package, which should make usage seamless. Is there a problem that you're trying to solve with this change?

@vdegenne
Copy link
Author

@vdegenne could you please explain your reasons for this change? We export both ESM and CJS for each package, which should make usage seamless. Is there a problem that you're trying to solve with this change?

Sorry I think it's a misunderstanding, I was trying to use @rollup/plugin-terser in rollup.config.TS and I had an error, adding "type": "module" manually into the package.json solved the issue... ...until I realized I was using "module": "NodeNext" in my ts config. I changed the value to Node and the error was gone.
I see this package is still providing CommonJS so I guess you are not going to accept this change any time soon.

@shellscape
Copy link
Collaborator

OK thanks for explaining. Yeah unfortunately we won't be moving to only ES exports soon.

@shellscape shellscape closed this Jan 1, 2024
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.

None yet

3 participants