Skip to content

chore(NA): updating used polyfills using 3rd party library#218020

Merged
mistic merged 22 commits intoelastic:mainfrom
mistic:update-used-polyfills
Apr 30, 2025
Merged

chore(NA): updating used polyfills using 3rd party library#218020
mistic merged 22 commits intoelastic:mainfrom
mistic:update-used-polyfills

Conversation

@mistic
Copy link
Contributor

@mistic mistic commented Apr 11, 2025

Closes https://github.com/elastic/kibana-operations/issues/267

This PR is a follow up from the webpack v5 upgrade which makes sure we stop using the old non maintained webpack v4 polyfills library and use instead a new supported library called node-stdlib-browser.

@mistic mistic added chore Team:Operations Kibana-Operations Team release_note:skip Skip the PR/issue when compiling release notes backport:prev-major v9.1.0 labels Apr 24, 2025
@mistic mistic self-assigned this Apr 25, 2025
@mistic mistic marked this pull request as ready for review April 29, 2025 18:39
@mistic mistic requested review from a team and kibanamachine as code owners April 29, 2025 18:39
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-operations (Team:Operations)

@kibanamachine
Copy link
Contributor

Starting backport for target branches: 8.17, 8.18, 8.19

https://github.com/elastic/kibana/actions/runs/14763854194

@kibanamachine
Copy link
Contributor

Starting backport for target branches: 8.17, 8.18, 8.19, 9.0

https://github.com/elastic/kibana/actions/runs/14763870176

@kibanamachine
Copy link
Contributor

💔 All backports failed

Status Branch Result
8.17 Backport failed because of merge conflicts
8.18 Backport failed because of merge conflicts
8.19 Backport failed because of merge conflicts

Manual backport

To create the backport manually run:

node scripts/backport --pr 218020

Questions ?

Please refer to the Backport tool documentation

@kibanamachine
Copy link
Contributor

💔 All backports failed

Status Branch Result
8.17 Backport failed because of merge conflicts
8.18 Backport failed because of merge conflicts

You might need to backport the following PRs to 8.18:
- Update rbush to v4 (main) (manual) (#219613)
8.19 Backport failed because of merge conflicts

You might need to backport the following PRs to 8.19:
- Update rbush to v4 (main) (manual) (#219613)
- [LockManager] Expose as package (#219220)
- [upgrade assistant] Create upgrade-assistant package, stub out storybook usage (#218705)
- Upgrade @elastic/charts to 69.2.1 (#216430)
9.0 Backport failed because of merge conflicts

You might need to backport the following PRs to 9.0:
- Update rbush to v4 (main) (manual) (#219613)
- [ska][x-pack] relocate api_integration tests [1] (#218470)
- Update OpenFeature (main) (#218569)

Manual backport

To create the backport manually run:

node scripts/backport --pr 218020

Questions ?

Please refer to the Backport tool documentation

mistic added a commit to mistic/kibana that referenced this pull request Apr 30, 2025
…18020)

Closes elastic/kibana-operations#267

This PR is a follow up from the webpack v5 upgrade which makes sure we
stop using the old non maintained webpack v4 polyfills library and use
instead a new supported library called `node-stdlib-browser`.

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
(cherry picked from commit aac2d47)

# Conflicts:
#	packages/kbn-optimizer/src/worker/webpack.config.ts
#	src/platform/packages/private/kbn-ui-shared-deps-npm/webpack.config.js
#	yarn.lock
mistic added a commit to mistic/kibana that referenced this pull request Apr 30, 2025
…18020)

Closes elastic/kibana-operations#267

This PR is a follow up from the webpack v5 upgrade which makes sure we
stop using the old non maintained webpack v4 polyfills library and use
instead a new supported library called `node-stdlib-browser`.

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
(cherry picked from commit aac2d47)

# Conflicts:
#	package.json
#	packages/kbn-optimizer/src/worker/webpack.config.ts
#	src/platform/packages/private/kbn-ui-shared-deps-npm/webpack.config.js
#	yarn.lock
mistic added a commit to mistic/kibana that referenced this pull request Apr 30, 2025
…18020)

Closes elastic/kibana-operations#267

This PR is a follow up from the webpack v5 upgrade which makes sure we
stop using the old non maintained webpack v4 polyfills library and use
instead a new supported library called `node-stdlib-browser`.

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
(cherry picked from commit aac2d47)

# Conflicts:
#	package.json
#	packages/kbn-optimizer/src/worker/webpack.config.ts
#	src/platform/packages/private/kbn-ui-shared-deps-npm/webpack.config.js
#	yarn.lock
mistic added a commit to mistic/kibana that referenced this pull request Apr 30, 2025
…18020)

Closes elastic/kibana-operations#267

This PR is a follow up from the webpack v5 upgrade which makes sure we
stop using the old non maintained webpack v4 polyfills library and use
instead a new supported library called `node-stdlib-browser`.

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
(cherry picked from commit aac2d47)

# Conflicts:
#	package.json
#	packages/kbn-optimizer/src/worker/webpack.config.ts
#	yarn.lock
@mistic
Copy link
Contributor Author

mistic commented Apr 30, 2025

💚 All backports created successfully

Status Branch Result
9.0
8.19
8.18
8.17

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id before after diff
apm 1874 1871 -3
automaticImport 782 777 -5
core 400 394 -6
dataUsage 120 117 -3
enterpriseSearch 1204 1142 -62
fleet 1181 1177 -4
graph 262 256 -6
infra 1392 1389 -3
kibanaUtils 166 160 -6
maps 1242 1233 -9
mapsEms 52 46 -6
ml 2370 2364 -6
profiling 281 275 -6
share 69 63 -6
uptime 773 770 -3
visTypeTimeseries 490 484 -6
total -140

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id before after diff
apm 2.6MB 2.5MB -9.9KB
automaticImport 1.1MB 1.1MB -27.0KB
cases 1.3MB 1.3MB +29.0B
console 186.4KB 185.8KB -621.0B
dataUsage 260.2KB 244.1KB -16.1KB
enterpriseSearch 1.2MB 1.2MB -43.8KB
fleet 1.7MB 1.7MB -23.5KB
graph 381.0KB 370.1KB -10.9KB
infra 1.2MB 1.1MB -9.6KB
maps 3.0MB 3.0MB -25.3KB
mapsEms 86.4KB 75.3KB -11.0KB
ml 5.3MB 5.3MB -11.0KB
profiling 370.7KB 359.7KB -11.0KB
securitySolution 9.1MB 9.1MB -2.0B
slo 904.8KB 906.5KB +1.8KB
uptime 494.9KB 485.0KB -9.9KB
visTypeTimeseries 482.6KB 471.8KB -10.8KB
total -218.8KB

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id before after diff
apm 35.6KB 35.5KB -100.0B
console 25.8KB 27.5KB +1.7KB
core 442.8KB 431.6KB -11.1KB
fleet 164.1KB 164.1KB -2.0B
graph 8.9KB 8.8KB -79.0B
infra 50.5KB 50.4KB -112.0B
kbnUiSharedDeps-npmDll 6.2MB 6.3MB +86.4KB
kbnUiSharedDeps-srcJs 3.7MB 3.7MB -10.9KB
kibanaUtils 66.1KB 55.2KB -11.0KB
maps 40.7KB 40.6KB -74.0B
mapsEms 6.0KB 6.0KB -94.0B
profiling 18.4KB 18.3KB -94.0B
share 59.7KB 48.8KB -10.9KB
uptime 42.9KB 42.8KB -105.0B
urlForwarding 4.8KB 6.5KB +1.7KB
visTypeTimeseries 17.6KB 17.6KB -89.0B
visTypeVega 34.7KB 34.1KB -621.0B
total +44.6KB
Unknown metric groups

async chunk count

id before after diff
infra 30 29 -1

History

cc @mistic

mistic added a commit that referenced this pull request May 1, 2025
…8020) (#219799)

# Backport

This will backport the following commits from `main` to `9.0`:
- [chore(NA): updating used polyfills using 3rd party library
(#218020)](#218020)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Tiago
Costa","email":"tiago.costa@elastic.co"},"sourceCommit":{"committedDate":"2025-04-30T20:35:22Z","message":"chore(NA):
updating used polyfills using 3rd party library (#218020)\n\nCloses
https://github.com/elastic/kibana-operations/issues/267\n\nThis PR is a
follow up from the webpack v5 upgrade which makes sure we\nstop using
the old non maintained webpack v4 polyfills library and use\ninstead a
new supported library called
`node-stdlib-browser`.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"aac2d4788ae588e3a999f90772a62fcfe2ad7755","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore","Team:Operations","release_note:skip","backport:prev-minor","backport:prev-major","ci:build-webpack-bundle-analyzer","v9.1.0"],"title":"chore(NA):
updating used polyfills using 3rd party
library","number":218020,"url":"https://github.com/elastic/kibana/pull/218020","mergeCommit":{"message":"chore(NA):
updating used polyfills using 3rd party library (#218020)\n\nCloses
https://github.com/elastic/kibana-operations/issues/267\n\nThis PR is a
follow up from the webpack v5 upgrade which makes sure we\nstop using
the old non maintained webpack v4 polyfills library and use\ninstead a
new supported library called
`node-stdlib-browser`.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"aac2d4788ae588e3a999f90772a62fcfe2ad7755"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/218020","number":218020,"mergeCommit":{"message":"chore(NA):
updating used polyfills using 3rd party library (#218020)\n\nCloses
https://github.com/elastic/kibana-operations/issues/267\n\nThis PR is a
follow up from the webpack v5 upgrade which makes sure we\nstop using
the old non maintained webpack v4 polyfills library and use\ninstead a
new supported library called
`node-stdlib-browser`.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"aac2d4788ae588e3a999f90772a62fcfe2ad7755"}}]}]
BACKPORT-->

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
mistic added a commit that referenced this pull request May 1, 2025
…18020) (#219801)

# Backport

This will backport the following commits from `main` to `8.19`:
- [chore(NA): updating used polyfills using 3rd party library
(#218020)](#218020)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Tiago
Costa","email":"tiago.costa@elastic.co"},"sourceCommit":{"committedDate":"2025-04-30T20:35:22Z","message":"chore(NA):
updating used polyfills using 3rd party library (#218020)\n\nCloses
https://github.com/elastic/kibana-operations/issues/267\n\nThis PR is a
follow up from the webpack v5 upgrade which makes sure we\nstop using
the old non maintained webpack v4 polyfills library and use\ninstead a
new supported library called
`node-stdlib-browser`.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"aac2d4788ae588e3a999f90772a62fcfe2ad7755","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore","Team:Operations","release_note:skip","backport:prev-minor","backport:prev-major","ci:build-webpack-bundle-analyzer","v9.1.0"],"title":"chore(NA):
updating used polyfills using 3rd party
library","number":218020,"url":"https://github.com/elastic/kibana/pull/218020","mergeCommit":{"message":"chore(NA):
updating used polyfills using 3rd party library (#218020)\n\nCloses
https://github.com/elastic/kibana-operations/issues/267\n\nThis PR is a
follow up from the webpack v5 upgrade which makes sure we\nstop using
the old non maintained webpack v4 polyfills library and use\ninstead a
new supported library called
`node-stdlib-browser`.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"aac2d4788ae588e3a999f90772a62fcfe2ad7755"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/218020","number":218020,"mergeCommit":{"message":"chore(NA):
updating used polyfills using 3rd party library (#218020)\n\nCloses
https://github.com/elastic/kibana-operations/issues/267\n\nThis PR is a
follow up from the webpack v5 upgrade which makes sure we\nstop using
the old non maintained webpack v4 polyfills library and use\ninstead a
new supported library called
`node-stdlib-browser`.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"aac2d4788ae588e3a999f90772a62fcfe2ad7755"}}]}]
BACKPORT-->

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
mistic added a commit that referenced this pull request May 1, 2025
…18020) (#219802)

# Backport

This will backport the following commits from `main` to `8.18`:
- [chore(NA): updating used polyfills using 3rd party library
(#218020)](#218020)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Tiago
Costa","email":"tiago.costa@elastic.co"},"sourceCommit":{"committedDate":"2025-04-30T20:35:22Z","message":"chore(NA):
updating used polyfills using 3rd party library (#218020)\n\nCloses
https://github.com/elastic/kibana-operations/issues/267\n\nThis PR is a
follow up from the webpack v5 upgrade which makes sure we\nstop using
the old non maintained webpack v4 polyfills library and use\ninstead a
new supported library called
`node-stdlib-browser`.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"aac2d4788ae588e3a999f90772a62fcfe2ad7755","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore","Team:Operations","release_note:skip","backport:prev-minor","backport:prev-major","ci:build-webpack-bundle-analyzer","v9.1.0"],"title":"chore(NA):
updating used polyfills using 3rd party
library","number":218020,"url":"https://github.com/elastic/kibana/pull/218020","mergeCommit":{"message":"chore(NA):
updating used polyfills using 3rd party library (#218020)\n\nCloses
https://github.com/elastic/kibana-operations/issues/267\n\nThis PR is a
follow up from the webpack v5 upgrade which makes sure we\nstop using
the old non maintained webpack v4 polyfills library and use\ninstead a
new supported library called
`node-stdlib-browser`.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"aac2d4788ae588e3a999f90772a62fcfe2ad7755"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/218020","number":218020,"mergeCommit":{"message":"chore(NA):
updating used polyfills using 3rd party library (#218020)\n\nCloses
https://github.com/elastic/kibana-operations/issues/267\n\nThis PR is a
follow up from the webpack v5 upgrade which makes sure we\nstop using
the old non maintained webpack v4 polyfills library and use\ninstead a
new supported library called
`node-stdlib-browser`.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"aac2d4788ae588e3a999f90772a62fcfe2ad7755"}}]}]
BACKPORT-->

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
mistic added a commit that referenced this pull request May 1, 2025
…18020) (#219811)

# Backport

This will backport the following commits from `main` to `8.17`:
- [chore(NA): updating used polyfills using 3rd party library
(#218020)](#218020)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Tiago
Costa","email":"tiago.costa@elastic.co"},"sourceCommit":{"committedDate":"2025-04-30T20:35:22Z","message":"chore(NA):
updating used polyfills using 3rd party library (#218020)\n\nCloses
https://github.com/elastic/kibana-operations/issues/267\n\nThis PR is a
follow up from the webpack v5 upgrade which makes sure we\nstop using
the old non maintained webpack v4 polyfills library and use\ninstead a
new supported library called
`node-stdlib-browser`.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"aac2d4788ae588e3a999f90772a62fcfe2ad7755","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore","Team:Operations","release_note:skip","backport:prev-minor","backport:prev-major","ci:build-webpack-bundle-analyzer","v9.1.0"],"title":"chore(NA):
updating used polyfills using 3rd party
library","number":218020,"url":"https://github.com/elastic/kibana/pull/218020","mergeCommit":{"message":"chore(NA):
updating used polyfills using 3rd party library (#218020)\n\nCloses
https://github.com/elastic/kibana-operations/issues/267\n\nThis PR is a
follow up from the webpack v5 upgrade which makes sure we\nstop using
the old non maintained webpack v4 polyfills library and use\ninstead a
new supported library called
`node-stdlib-browser`.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"aac2d4788ae588e3a999f90772a62fcfe2ad7755"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/218020","number":218020,"mergeCommit":{"message":"chore(NA):
updating used polyfills using 3rd party library (#218020)\n\nCloses
https://github.com/elastic/kibana-operations/issues/267\n\nThis PR is a
follow up from the webpack v5 upgrade which makes sure we\nstop using
the old non maintained webpack v4 polyfills library and use\ninstead a
new supported library called
`node-stdlib-browser`.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"aac2d4788ae588e3a999f90772a62fcfe2ad7755"}}]}]
BACKPORT-->

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
akowalska622 pushed a commit to akowalska622/kibana that referenced this pull request May 29, 2025
…18020)

Closes elastic/kibana-operations#267

This PR is a follow up from the webpack v5 upgrade which makes sure we
stop using the old non maintained webpack v4 polyfills library and use
instead a new supported library called `node-stdlib-browser`.

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants