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

🐛 Improve compatibility with AMD module systems #1000

Merged
merged 1 commit into from
Jul 26, 2022

Conversation

wwilsman
Copy link
Contributor

What is this?

Some older implementations of AMD module loading systems might throw an error when the first argument to define a module is not the name of the module itself. This PR adds the package name to the AMD section of the generated bundle output for rollup builds.

Some older implementations of AMD module loading systems might throw an error when the first
argument to define a module is not the name of the module itself.
@wwilsman wwilsman added the 🐛 bug Something isn't working label Jul 26, 2022
@wwilsman wwilsman requested a review from Robdel12 July 26, 2022 17:57
Copy link
Contributor

@Robdel12 Robdel12 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🏁

@Kraindrie
Copy link

Daghehh

@wwilsman wwilsman merged commit 1a7b098 into master Jul 26, 2022
@wwilsman wwilsman deleted the ww/name-amd-browser-bundles branch July 26, 2022 18:07
@dfreeman
Copy link

dfreeman commented Jul 28, 2022

@wwilsman This seems to have broken @percy/ember. It uses some arcane build shenanigans to include @percy/sdk-utils, and the code that produces falls over when a module name is provided to define.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants