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

swcMinify breaks CountUp package #30414

Closed
ch3rn1k opened this issue Oct 27, 2021 · 1 comment · Fixed by #30790
Closed

swcMinify breaks CountUp package #30414

ch3rn1k opened this issue Oct 27, 2021 · 1 comment · Fixed by #30790
Milestone

Comments

@ch3rn1k
Copy link

ch3rn1k commented Oct 27, 2021

What version of Next.js are you using?

12.0.1

What version of Node.js are you using?

14.17.0

What browser are you using?

Chrome

What operating system are you using?

macOS

How are you deploying your application?

next start

Describe the Bug

When compiling with swcMinify: true it breaks CountUp react component and each number became as undefined

Expected Behavior

Working react component, without this feature works fine, but I want to use it

To Reproduce

  1. Install NextJS
  2. Create config with swcMinify
  3. Install CountUp package
  4. Create any component and then build an app
@ch3rn1k ch3rn1k added the bug Issue was opened via the bug report template. label Oct 27, 2021
@ch3rn1k ch3rn1k changed the title swcMinify breaks CountUp component swcMinify breaks CountUp package Oct 27, 2021
@timneutkens timneutkens added area: SWC Minify and removed bug Issue was opened via the bug report template. labels Oct 31, 2021
@timneutkens timneutkens added this to the 12.0.x milestone Oct 31, 2021
@kodiakhq kodiakhq bot closed this as completed in #30790 Nov 2, 2021
kodiakhq bot pushed a commit that referenced this issue Nov 2, 2021
## Bug

- [ ] Related issues linked using `fixes #number`
- [ ] Integration tests added
- [ ] Errors have helpful link attached, see `contributing.md`

## Feature

- [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR.
- [ ] Related issues linked using `fixes #number`
- [ ] Integration tests added
- [ ] Documentation added
- [ ] Telemetry added. In case of a feature if it's used or not.
- [ ] Errors have helpful link attached, see `contributing.md`

## Documentation / Examples

- [ ] Make sure the linting passes by running `yarn lint`



This PR applies

 - swc-project/swc#2610

This increases the pass limit (which is required to prevent hanging) from 30 to 100.
Fixes #30636.

 - swc-project/swc#2625

This marks assignment with operators as `usage`+ `assign`. Previously it was only `assisgn`. This is to preserve assignments to variables used like `(a += '').split('.'))`.

Fixes #30414.

---

I expect this to fix some more issues on next.js repository, but I didn't list them because it's not tested.
@balazsorban44
Copy link
Member

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

@vercel vercel locked as resolved and limited conversation to collaborators Jan 27, 2022
natew pushed a commit to natew/next.js that referenced this issue Feb 16, 2022
## Bug

- [ ] Related issues linked using `fixes #number`
- [ ] Integration tests added
- [ ] Errors have helpful link attached, see `contributing.md`

## Feature

- [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR.
- [ ] Related issues linked using `fixes #number`
- [ ] Integration tests added
- [ ] Documentation added
- [ ] Telemetry added. In case of a feature if it's used or not.
- [ ] Errors have helpful link attached, see `contributing.md`

## Documentation / Examples

- [ ] Make sure the linting passes by running `yarn lint`



This PR applies

 - swc-project/swc#2610

This increases the pass limit (which is required to prevent hanging) from 30 to 100.
Fixes vercel#30636.

 - swc-project/swc#2625

This marks assignment with operators as `usage`+ `assign`. Previously it was only `assisgn`. This is to preserve assignments to variables used like `(a += '').split('.'))`.

Fixes vercel#30414.

---

I expect this to fix some more issues on next.js repository, but I didn't list them because it's not tested.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants