build(deps-dev): bump webpack from 5.94.0 to 5.105.0 in /examples/emberjs in the npm_and_yarn group across 1 directory

[dependabot]

Bumps the npm_and_yarn group with 1 update in the /examples/emberjs directory: webpack.

Updates webpack from 5.94.0 to 5.105.0

Release notes

Sourced from webpack's releases.

v5.105.0

Minor Changes

• Allow resolving worker module by export condition name when using new Worker() (by @​hai-x in #20353)

• Detect conditional imports to avoid compile-time linking errors for non-existent exports. (by @​hai-x in #20320)

• Added the tsconfig option for the resolver options (replacement for tsconfig-paths-webpack-plugin). Can be false (disabled), true (use the default tsconfig.json file to search for it), a string path to tsconfig.json, or an object with configFile and references options. (by @​alexander-akait in #20400)

• Support import.defer() for context modules. (by @​ahabhgk in #20399)

• Added support for array values ​​to the devtool option. (by @​hai-x in #20191)

• Improve rendering node built-in modules for ECMA module output. (by @​hai-x in #20255)

• Unknown import.meta properties are now determined at runtime instead of being statically analyzed at compile time. (by @​xiaoxiaojx in #20312)

Patch Changes

• Fixed ESM default export handling for .mjs files in Module Federation (by @​y-okt in #20189)

• Optimized import.meta.env handling in destructuring assignments by using cached stringified environment definitions. (by @​xiaoxiaojx in #20313)

• Respect the stats.errorStack option in stats output. (by @​samarthsinh2660 in #20258)

• Fixed a bug where declaring a module variable in module scope would conflict with the default moduleArgument. (by @​xiaoxiaojx in #20265)

• Fix VirtualUrlPlugin to set resourceData.context for proper module resolution. Previously, when context was not set, it would fallback to the virtual scheme path (e.g., virtual:routes), which is not a valid filesystem path, causing subsequent resolve operations to fail. (by @​xiaoxiaojx in #20390)

• Fixed Worker self-import handling to support various URL patterns (e.g., import.meta.url, new URL(import.meta.url), new URL(import.meta.url, import.meta.url), new URL("./index.js", import.meta.url)). Workers that resolve to the same module are now properly deduplicated, regardless of the URL syntax used. (by @​xiaoxiaojx in #20381)

• Reuse the same async entrypoint for the same Worker URL within a module to avoid circular dependency warnings when multiple Workers reference the same resource. (by @​xiaoxiaojx in #20345)

• Fixed a bug where a self-referencing dependency would have an unused export name when imported inside a web worker. (by @​samarthsinh2660 in #20251)

• Fix missing export generation when concatenated modules in different chunks share the same runtime in module library bundles. (by @​hai-x in #20346)

• Fixed import.meta.env.xxx behavior: when accessing a non-existent property, it now returns empty object instead of full object at runtime. (by @​xiaoxiaojx in #20289)

• Improved parsing error reporting by adding a link to the loader documentation. (by @​gaurav10gg in #20244)

• Fix typescript types. (by @​alexander-akait in #20305)

• Add declaration for unused harmony import specifier. (by @​hai-x in #20286)

• Fix compressibility of modules while retaining portability. (by @​dmichon-msft in #20287)

• Optimize source map generation: only include ignoreList property when it has content, avoiding empty arrays in source maps. (by @​xiaoxiaojx in #20319)

• Preserve star exports for dependencies in ECMA module output. (by @​hai-x in #20293)

... (truncated)

Changelog

Sourced from webpack's changelog.

5.105.0

Minor Changes

• Allow resolving worker module by export condition name when using new Worker() (by @​hai-x in #20353)

• Detect conditional imports to avoid compile-time linking errors for non-existent exports. (by @​hai-x in #20320)

• Added the tsconfig option for the resolver options (replacement for tsconfig-paths-webpack-plugin). Can be false (disabled), true (use the default tsconfig.json file to search for it), a string path to tsconfig.json, or an object with configFile and references options. (by @​alexander-akait in #20400)

• Support import.defer() for context modules. (by @​ahabhgk in #20399)

• Added support for array values ​​to the devtool option. (by @​hai-x in #20191)

• Improve rendering node built-in modules for ECMA module output. (by @​hai-x in #20255)

• Unknown import.meta properties are now determined at runtime instead of being statically analyzed at compile time. (by @​xiaoxiaojx in #20312)

Patch Changes

• Fixed ESM default export handling for .mjs files in Module Federation (by @​y-okt in #20189)

• Optimized import.meta.env handling in destructuring assignments by using cached stringified environment definitions. (by @​xiaoxiaojx in #20313)

• Respect the stats.errorStack option in stats output. (by @​samarthsinh2660 in #20258)

• Fixed a bug where declaring a module variable in module scope would conflict with the default moduleArgument. (by @​xiaoxiaojx in #20265)

• Fix VirtualUrlPlugin to set resourceData.context for proper module resolution. Previously, when context was not set, it would fallback to the virtual scheme path (e.g., virtual:routes), which is not a valid filesystem path, causing subsequent resolve operations to fail. (by @​xiaoxiaojx in #20390)

• Fixed Worker self-import handling to support various URL patterns (e.g., import.meta.url, new URL(import.meta.url), new URL(import.meta.url, import.meta.url), new URL("./index.js", import.meta.url)). Workers that resolve to the same module are now properly deduplicated, regardless of the URL syntax used. (by @​xiaoxiaojx in #20381)

• Reuse the same async entrypoint for the same Worker URL within a module to avoid circular dependency warnings when multiple Workers reference the same resource. (by @​xiaoxiaojx in #20345)

• Fixed a bug where a self-referencing dependency would have an unused export name when imported inside a web worker. (by @​samarthsinh2660 in #20251)

• Fix missing export generation when concatenated modules in different chunks share the same runtime in module library bundles. (by @​hai-x in #20346)

• Fixed import.meta.env.xxx behavior: when accessing a non-existent property, it now returns empty object instead of full object at runtime. (by @​xiaoxiaojx in #20289)

• Improved parsing error reporting by adding a link to the loader documentation. (by @​gaurav10gg in #20244)

• Fix typescript types. (by @​alexander-akait in #20305)

• Add declaration for unused harmony import specifier. (by @​hai-x in #20286)

• Fix compressibility of modules while retaining portability. (by @​dmichon-msft in #20287)

• Optimize source map generation: only include ignoreList property when it has content, avoiding empty arrays in source maps. (by @​xiaoxiaojx in #20319)

... (truncated)

Commits

• 1486f9a chore(release): new release
• 1a517f6 feat: added the tsconfig option for the resolver options (#20400)
• 7b3b0f7 feat: support import.defer() for context modules
• c4a6a92 refactor: more types and increase types coverage
• 5ecc58d feat: consider asset module as side-effect-free (#20352)
• cce0f69 test: avoid comma operator in BinaryMiddleware test (#20398)
• cd4793d feat: support import specifier guard (#20320)
• fe48655 docs: update examples (#20397)
• de107f8 fix(VirtualUrlPlugin): set resourceData.context to avoid invalid fallback (#2...
• a656ab1 test: add self-import test case for dynamic import (#20389)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for webpack since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[guibranco]

Automatically approved by gstraccini[bot]

[socket-security]

Caution

Review the following alerts detected in dependencies.

According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Block		Embedded URLs or IPs: npm @webassemblyjs/ast URLs: https://webassembly.github.io/spec/core/binary/modules.html#binary-module, https://webassembly.github.io/spec/core/text/modules.html#text-module Location: Package overview From: examples/emberjs/package-lock.json → npm/@webassemblyjs/[email protected] ℹ Read more on: This package | This alert | What are URL strings? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Review all remote URLs to ensure they are intentional, pointing to trusted sources, and not being used for data exfiltration or loading untrusted code at runtime. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@webassemblyjs/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Potential code anomaly (AI signal): npm @webassemblyjs/wasm-parser is 100.0% likely to have a medium risk anomaly Notes: The code is a legitimate WebAssembly binary decoder/AST builder. It decodes a WASM module into a rich AST representation without performing harmful actions, network activity, or data exfiltration. The primary security considerations are ensuring trust in the library's source and keeping dependencies current, as with any third-party tool. If kept updated and used with proper input validation, the component poses no immediate malicious risk based on this fragment. Confidence: 1.00 Severity: 0.60 From: examples/emberjs/package-lock.json → npm/@webassemblyjs/[email protected] ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@webassemblyjs/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Environment variable access: npm baseline-browser-mapping Location: Package overview From: examples/emberjs/package-lock.json → npm/[email protected] → npm/@ember/[email protected] → npm/[email protected] → npm/[email protected] → npm/[email protected] → npm/[email protected] → npm/@glimmer/[email protected] → npm/[email protected] → npm/[email protected] → npm/[email protected] → npm/[email protected] ℹ Read more on: This package | This alert | What is environment variable access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Environment variable access: npm baseline-browser-mapping Env Vars: BROWSERSLIST_IGNORE_OLD_DATA Location: Package overview From: examples/emberjs/package-lock.json → npm/[email protected] → npm/@ember/[email protected] → npm/[email protected] → npm/[email protected] → npm/[email protected] → npm/[email protected] → npm/@glimmer/[email protected] → npm/[email protected] → npm/[email protected] → npm/[email protected] → npm/[email protected] ℹ Read more on: This package | This alert | What is environment variable access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Environment variable access: npm baseline-browser-mapping Env Vars: BASELINE_BROWSER_MAPPING_IGNORE_OLD_DATA Location: Package overview From: examples/emberjs/package-lock.json → npm/[email protected] → npm/@ember/[email protected] → npm/[email protected] → npm/[email protected] → npm/[email protected] → npm/[email protected] → npm/@glimmer/[email protected] → npm/[email protected] → npm/[email protected] → npm/[email protected] → npm/[email protected] ℹ Read more on: This package | This alert | What is environment variable access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Embedded URLs or IPs: npm fast-uri URLs: https://example.com/foo#bar, 10.10.10.10, example.com, https://datatracker.ietf.org/doc/html/rfc3986#section-5.2.4, example.com:1/path?query#fragment, uri://example.com:9000, 10.10.10.10.example.com, 129.144.52.38, ws://example.com, ws://example.com/foo, ws://example.com/foo?bar, wss://example.com, wss://example.com/foo?bar, wss://example.com/foo, example.com:123/one/two.three?q1=a1&q2=a2#body, example.com:123, 10.10.000.10, 01.01.01.01, uri://10.10.10.10.example.com/en/process, http://example.com/, http://example.com/foo, http://example.com/foo/, http://example.org/~user, http://example.org/%7euser, http://abc.com:80/~smith/home.html, http://abc.com/~smith/home.html, abc.com, http://ABC.com/%7Esmith/home.html, http://ABC.com:/%7esmith/home.html, HTTP://ABC.COM, http://abc.com/, http://example.com:/, http://example.com:80/, https://example.com, https://example.com:443/, https://example.com:/, WS://ABC.COM:80/chat#one, ws://abc.com/chat, WSS://ABC.COM:443/chat#one, wss://abc.com/chat, www.g.com/, www.g.com/adf%0Agf, www.g.com/error%0A/, uri://www.example.org/red%09ros, uri://www.example.org/red%09ros%C3%A9#red, 192.068.001.000, 192.68.1.0, example.org, uri://xn--rsum-bpad.example.org, uri://www.example.org/D%C3%BCrst, uri://www.example.org/D, uri://www.example.org/D%FCrst, uri://xn--99zt52a.example.org/%e2%80%ae, uri://xn--99zt52a.example.org/%E2%80%AE, example.com?subject=current-issue, example.com?body=send%20current-issue, example.com?body=send%20current-issue%0D%0Asend%20index, example.org?In-Reply-To=%[email protected]%3E, example.com?body=subscribe%20bamboo-l, [email protected]&body=hello, [email protected]?body=hello, example.com?blat=foop, example.org?subject=caf%C3%A9, example.org?subject=%3D%3Futf-8%3FQ%3Fcaf%3DC3%3DA9%3F%3D, example.org?subject=%3D%3Fiso-8859-1%3FQ%3Fcaf%3DE9%3F%3D, example.org?subject=caf%C3%A9&body=caf%C3%A9, 86.example.org?subject=Test&body=NATTO, xn--99zt52a.example.org, example.com?body=current-issue, xn--99zt52a.example.org?subject=Test&body=NATTO, ws://example.com/chat, ws://example.com/foo?bar=baz, ws://example.com/?bar=baz, ws://example.com:80/foo#hash, wss://example.com/chat, wss://example.com/foo?bar=baz, wss://example.com/?bar=baz, wss://example.com:443/foo#hash, mple.com, https://datatracker.ietf.org/doc/html/rfc5954#section-4.1 Location: Package overview From: examples/emberjs/package-lock.json → npm/[email protected] ℹ Read more on: This package | This alert | What are URL strings? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Review all remote URLs to ensure they are intentional, pointing to trusted sources, and not being used for data exfiltration or loading untrusted code at runtime. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[github-actions]

Infisical secrets check: ✅ No secrets leaked!

💻 Scan logs

2026-02-11T15:01:31Z INF scanning for exposed secrets...
3:01PM INF 1459 commits scanned.
2026-02-11T15:01:35Z INF scan completed in 3.33s
2026-02-11T15:01:35Z INF no leaks found

[github-actions]

Summary

Status	Count
🔍 Total	455
✅ Successful	185
⏳ Timeouts	0
🔀 Redirected	16
👻 Excluded	253
❓ Unknown	0
🚫 Errors	1
⛔ Unsupported	0

Errors per input

Errors in ./data/bancos.md

• [ERROR] https://www.ouribank.com.br/ | Network error: Connection failed. Check network connectivity and firewall settings

Redirects per input

Redirects in ./data/bancos.md

• [200] https://www.bancoinbursa.com/ | Redirect: Followed 2 redirects resolving to the final status of: OK. Redirects: https://www.bancoinbursa.com/ --> https://www.bancoinbursa.com/login/useraccess.asp --> https://www.inbursaenlinea.com/inbursabanco/login
• [200] https://www.bancokdb.com.br/home.html | Redirect: Followed 1 redirect resolving to the final status of: OK. Redirects: https://www.bancokdb.com.br/home.html --> https://www.kdb.co.kr/BZCOWS00N01.act?wcmsPath=/hmp/ch/gm/ba/CHGMBA0200.html&GmBrnId=BZ&_mnuId=IHIHGM1004&GmMlngTc=pt&jobNotice=Yhome.html
• [200] https://www.bancooriginal.com.br/ | Redirect: Followed 1 redirect resolving to the final status of: OK. Redirects: https://www.bancooriginal.com.br/ --> https://www.original.com.br/
• [200] https://www.bancovotorantim.com.br/ | Redirect: Followed 2 redirects resolving to the final status of: OK. Redirects: https://www.bancovotorantim.com.br/ --> https://www.bancobv.com.br/ --> https://www.bv.com.br/
• [200] https://www.bancovw.com.br/ | Redirect: Followed 1 redirect resolving to the final status of: OK. Redirects: https://www.bancovw.com.br/ --> https://www.vwfs.com.br/
• [200] https://www.bip.b.br/ | Redirect: Followed 2 redirects resolving to the final status of: OK. Redirects: https://www.bip.b.br/ --> http://ri.bancopleno.com.br/ --> http://ri.bancopleno.com.br/ri
• [200] https://www.br.scotiabank.com/ | Redirect: Followed 1 redirect resolving to the final status of: OK. Redirects: https://www.br.scotiabank.com/ --> https://www.gbm.scotiabank.com/en/about-overview/our-global-presence/brazil/brazil-portuguese.html
• [200] https://www.bradescobbi.com.br/ | Redirect: Followed 2 redirects resolving to the final status of: OK. Redirects: https://www.bradescobbi.com.br/ --> https://bradescobbi.com.br/ --> https://bradescobbi.com.br/home
• [200] https://www.bradescofinanciamentos.com.br/ | Redirect: Followed 1 redirect resolving to the final status of: OK. Redirects: https://www.bradescofinanciamentos.com.br/ --> https://financiamentos.bradesco/
• [200] https://www.bs2.com/banco/ | Redirect: Followed 2 redirects resolving to the final status of: OK. Redirects: https://www.bs2.com/banco/ --> https://www.bancobs2.com.br/banco/ --> https://www.bancobs2.com.br/banco-bs2-amplia-oferta-para-publico-pj-e-lanca-unidade-de-negocios-de-banking-as-a-service/
• [200] https://www.c6bank.com/ | Redirect: Followed 1 redirect resolving to the final status of: OK. Redirects: https://www.c6bank.com/ --> https://www.c6bank.com.br/
• [200] https://www.citibank.com.br/ | Redirect: Followed 2 redirects resolving to the final status of: OK. Redirects: https://www.citibank.com.br/ --> https://corporateportal.brazil.citibank.com/ --> https://corporateportal.brazil.citibank.com/index.htm
• [200] https://www.intesasanpaolobrasil.com.br/ | Redirect: Followed 1 redirect resolving to the final status of: OK. Redirects: https://www.intesasanpaolobrasil.com.br/ --> https://www.intesasanpaolobrasil.com.br/pt/
• [200] https://www.jpmorgan.com/ | Redirect: Followed 1 redirect resolving to the final status of: OK. Redirects: https://www.jpmorgan.com/ --> https://www.jpmorgan.com/global
• [200] https://www.picpay.com.br/ | Redirect: Followed 1 redirect resolving to the final status of: OK. Redirects: https://www.picpay.com.br/ --> https://picpay.com/pt-br/pf
• [200] https://www.sicredi.com.br/ | Redirect: Followed 1 redirect resolving to the final status of: OK. Redirects: https://www.sicredi.com.br/ --> https://www.sicredi.com.br/home/
  Full Github Actions output

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud