requirejs([''vimeo/player''], ...) doesn't work

[0m3r]

Preconditions and environment

• Magento 2.4.5 after this commit https://github.com/magento/magento2/commit/2b98dc6517c4148cb98afb25fa86efd63c348948#diff-6bbf557f143626ce945375a3488dcdf7a55ecabf84cc53f4413197ffc3c5d3e7

Steps to reproduce

1. open Magento 2.4.5 home page
2. press F12 to open the dev toolbar
3. run js code in a console

window.require(['jquery', 'vimeo/player', 'vimeo/vimeo-wrapper'], function (){console.log(arguments)});

jquery works vimeo/* doesn't work

because code here https://github.com/magento/magento2/blob/2b98dc6517c4148cb98afb25fa86efd63c348948/app/code/Magento/Theme/view/base/requirejs-config.js#L49

@anzin @andrewbess

Expected result

console without errors

Actual result

console with js errors

require.js:168 Uncaught Error: Script error for "vimeo/player/player"
require.js:168 Uncaught Error: Script error for "vimeo/player/vimeo-wrapper"

Additional information

I think the problem is here

https://github.com/magento/magento2/blob/2b98dc6517c4148cb98afb25fa86efd63c348948/app/code/Magento/Theme/view/base/requirejs-config.js#L49

https://github.com/magento/magento2/commit/2b98dc6517c4148cb98afb25fa86efd63c348948#diff-6bbf557f143626ce945375a3488dcdf7a55ecabf84cc53f4413197ffc3c5d3e7

Release note

No response

Triage and priority

• [ ] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• [ ] Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• [X] Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• [ ] Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• [ ] Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant[bot]]

Hi @0m3r. Thank you for your report. To speed up processing of this issue, make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, review the Magento Contributor Assistant documentation.

Add a comment to assign the issue: @magento I am working on this

To learn more about issue processing workflow, refer to the Code Contributions.

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

  :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

:clock10: You can find the schedule on the Magento Community Calendar page.

:telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

:pencil2: Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[0m3r]

Sorry look like the problem is in Page Builder https://github.com/magento/magento2-page-builder/commit/a8b806386305712b6086bd4594aab817d5e34094

https://github.com/magento/magento2-page-builder/commit/a8b806386305712b6086bd4594aab817d5e34094#r80397027