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

Investigate rollup-common-js bug #285

Closed
luckyrat opened this issue Oct 22, 2020 · 1 comment
Closed

Investigate rollup-common-js bug #285

luckyrat opened this issue Oct 22, 2020 · 1 comment

Comments

@luckyrat
Copy link
Member

Version 2.23.1 of rollup-commonjs is the last one that works properly without triggering runtime errors. I've managed to upgrade to the latest version but it appears that something in the mammoth PR rollup/rollup/pull/3710 breaks object-shorthand assignments so in a few cases we have to write messy code like this from Notifications.vue:

import { tooltipDelay } from "../../common/Timings";

export default {
    data: () => ({
        tooltipDelay: tooltipDelay // short-hand assignment breaks rollup-commonjs (gets converted to something like common.x)
    }),

No value of output.interop makes a difference and neither does externalLiveBindings: false or freeze: false.

The bug occurs even when Terser is disabled so doesn't appear to be a simple re-ordering of when that optimisation gets executed. I wonder if it relates to various rollup commits that reference "de-optimisation". Something is perhaps no longer being de-optimised like it used to be.

Runtime errors introduced by build tooling are never fun but since I've found a workaround I can postpone further investigation for the time being.

@luckyrat
Copy link
Member Author

luckyrat commented Jun 6, 2024

We no longer depend on rollup-commonjs

@luckyrat luckyrat closed this as completed Jun 6, 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

No branches or pull requests

1 participant