Skip to content

Conversation

@pull
Copy link

@pull pull bot commented May 23, 2021

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

@atomist atomist bot added auto-branch-delete:on-close Delete branch when pull request gets closed auto-merge-method:merge Auto-merge with merge commit auto-merge:on-bpr-success Auto-merge on passed branch protection rule labels May 23, 2021
@pull pull bot added ⤵️ pull and removed auto-branch-delete:on-close Delete branch when pull request gets closed labels May 23, 2021
@codecov
Copy link

codecov bot commented May 23, 2021

Welcome to Codecov 🎉

Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.

Thanks for integrating Codecov - We've got you covered ☂️

renovate bot and others added 30 commits December 26, 2025 05:40
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
* fix(deps): update swc monorepo

* Adapt tested error messages

---------

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: Lukas Taegert-Atkinson <lukas.taegert-atkinson@tngtech.com>
#6222)

* Apply to adjust the description of the command-line parameter 'rollup -c'.

I think the following description is more suitable for everyone to understand:

`
-c, --config <filename>     Use this config file (if argument is used but value is unspecified, Rollup will try to load configuration files in the following order: rollup.config.mjs -> rollup.config.cjs -> rollup.config.js)
`

* Format the CLI parameter description text.

* Synchronously update the content of 'cli/help.md'.

* Correct formatting in cli/help.md

Fix formatting inconsistencies in help documentation.

---------

Co-authored-by: Lukas Taegert-Atkinson <lukastaegert@users.noreply.github.com>
* Deduplicate help.md

We use vitepress features to directly include and truncate the help.md file. We
use a VSCode region to trim the CLI options, which means we need to filter the
comments when loading the file.

* Update generated bindings

There were some changes that were not committed with some dependency update.

* Update options test

* Improve plugin name

* Add test to improve coverage

* Apply Copilot suggestions

* Fix test
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
fix(deps): update swc monorepo

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
* OpenBSD support

* OpenBSD support touch up
- replace missing matrix settings with hardcodes
- make test job depend on build-openbsd
- added missing triplet to package.json

* Fix directory name

* Remove OS version from artifact name

This should help NAPI-RS to properly identify the artifact

---------

Co-authored-by: Lukas Taegert-Atkinson <lukastaegert@users.noreply.github.com>
Co-authored-by: Lukas Taegert-Atkinson <lukas.taegert-atkinson@tngtech.com>
* Fix artifact names for openbsd

* Fix test for pre-release versions

* 4.55.1-0
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
* chore(deps): update dependency globals to v17

* Fix audit

---------

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: Lukas Taegert-Atkinson <lukas.taegert-atkinson@tngtech.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
* fix(deps): lock file maintenance minor/patch updates

* Ignore vulnerability for a month

As this is our test framework, it is not critical.

---------

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: Lukas Taegert-Atkinson <lukas.taegert-atkinson@tngtech.com>
* Add test

* Sort manual chunks by module execution order

* Regression
* Extend instruction file

* Fix semicolon insertion by never moving to the end

Also revert previous hack to in ExpressionStatement that fixes the issue in some
situations.
* Do not always include entire namespace when used as variable

* Refine export handling in module

Add general caching. The idea is to eventually merge this with the caching in
NamespaceVariabe.getMemberVariables

* Use cached exports in NamespaceVariable

* Replace usages of cached namespace variables

* Use cached map to get export names for variables

* Use cached map in more places

* Use cached exports to replace list of export names

* Separate namespace- and all-export-inclusion

* Refine namespace inclusion

* Break early in some loop

* Store ImportExpression resolution only on Node

This will make it easier to handle includes etc.

* Dynamically include dynamic import members

Instead of doing static analysis, this dynamically links the namespace to its
usage.
Currently, this is not as good, some test cases need to be analyzed if we can
improve here.

* Improve tree-shaking to match most of the old behaviour

* It was not easily to support optimizing (await import()).foo() because we
  cannot easily track if `foo` accesses `this`, in which case it could see the
  entire namespace. Added a regression test for this.
* As .catch and .finally do not change property inclusion, we can now optimize
  cases where a .catch or .finally is followed by a .then
* There was a bug in the synthetic namespace inclusion. Fixing this allows
tree-shaking for synthetic namespaces.

* Ensure Promise handler return value is deoptimized for now

* Add test for deep object property tree-shaking

* Avoid some property accesses and improve names

* Remove TODO

* Ensure catch and finally handlers are always included and deoptimized

This also simplifies return value deoptimization

* Reinstate system default export test

* Clarify synthetic named export test
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

⤵️ pull merge-conflict Resolve conflicts manually

Projects

None yet

Development

Successfully merging this pull request may close these issues.