Skip to content

build: fix incorrect amd module names #14786

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

Merged

Conversation

devversion
Copy link
Member

  • Our UMD bundles currently have wrong AMD module names for secondary entry-points which are dash-cased. e.g. AMD module name for the bottom-sheet is @angular/material/bottomSheet.
  • Our UMD bundles currently reference incorrect rollup globals. e.g. the AMD module name is ng.material-experimental.{secondary}, while it should be ng.materialExperimental.

@devversion devversion added pr: merge safe target: patch This PR is targeted for the next patch release labels Jan 10, 2019
@devversion devversion requested a review from jelbourn as a code owner January 10, 2019 16:54
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Jan 10, 2019
@devversion devversion force-pushed the build/fix-incorrect-amd-module-names branch from fb706bd to e5ef0fc Compare January 10, 2019 17:23
@devversion devversion force-pushed the build/fix-incorrect-amd-module-names branch 2 times, most recently from bb5ce06 to 465f2a3 Compare January 10, 2019 18:27
* Our UMD bundles currently have wrong AMD module names for secondary entry-points which are dash-cased. e.g. AMD module name for the bottom-sheet is `@angular/material/bottomSheet`.
* Our UMD bundles currently reference incorrect rollup globals. e.g. the AMD module name is `ng.material-experimental.{secondary}`, while it should be `ng.materialExperimental`.
@devversion devversion force-pushed the build/fix-incorrect-amd-module-names branch from 465f2a3 to 54b4c04 Compare January 10, 2019 18:28
Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

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

LGTM

@jelbourn jelbourn added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Jan 10, 2019
@andrewseguin andrewseguin merged commit 5d86a1f into angular:master Jan 11, 2019
andrewseguin pushed a commit that referenced this pull request Jan 11, 2019
* Our UMD bundles currently have wrong AMD module names for secondary entry-points which are dash-cased. e.g. AMD module name for the bottom-sheet is `@angular/material/bottomSheet`.
* Our UMD bundles currently reference incorrect rollup globals. e.g. the AMD module name is `ng.material-experimental.{secondary}`, while it should be `ng.materialExperimental`.
josephperrott pushed a commit to josephperrott/components that referenced this pull request Jan 14, 2019
* Our UMD bundles currently have wrong AMD module names for secondary entry-points which are dash-cased. e.g. AMD module name for the bottom-sheet is `@angular/material/bottomSheet`.
* Our UMD bundles currently reference incorrect rollup globals. e.g. the AMD module name is `ng.material-experimental.{secondary}`, while it should be `ng.materialExperimental`.
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 10, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants