Skip to content

build: remove hard-coded karma systemjs config #18025

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

Removes the hard-coded Karma SystemJS config in favor of a shared SystemJS
config that is used by both the dev-app and the legacy unit tests.

The config is generated through Bazel and leverages the
entry-point/package configuration we need to main in Bazel. That way we
only have one canonical place for package/entry-point configuration (the
config.bzl files per package).

@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Dec 21, 2019
@devversion devversion force-pushed the build/share-systemjs-generated-config branch from a3df418 to 9e21d6b Compare December 21, 2019 11:36
@devversion devversion marked this pull request as ready for review December 21, 2019 13:44
@devversion devversion requested review from jelbourn and a team as code owners December 21, 2019 13:44
@devversion devversion added pr: merge safe target: patch This PR is targeted for the next patch release labels Dec 21, 2019
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, just needs rebase

Tangent: did you mention potentially switching to require.js at some point?

Removes the hard-coded Karma SystemJS config in favor of a shared SystemJS
config that is used by both the dev-app and the legacy unit tests.

The config is generated through Bazel and leverages the
entry-point/package configuration we need to main in Bazel. That way we
only have one canonical place for package/entry-point configuration (the
`config.bzl` files per package).
@devversion devversion force-pushed the build/share-systemjs-generated-config branch from 9e21d6b to b36c5e6 Compare January 15, 2020 07:53
@jelbourn jelbourn added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Jan 16, 2020
@jelbourn jelbourn merged commit 16159b3 into angular:master Jan 16, 2020
@devversion
Copy link
Member Author

@jelbourn I wanted to reply on the require.js question. Yes, ultimately it would be good to switch to require.js since that is used by default in the Karma Bazel rules, and in ts_devserver.

yifange pushed a commit to yifange/components that referenced this pull request Jan 30, 2020
Removes the hard-coded Karma SystemJS config in favor of a shared SystemJS
config that is used by both the dev-app and the legacy unit tests.

The config is generated through Bazel and leverages the
entry-point/package configuration we need to main in Bazel. That way we
only have one canonical place for package/entry-point configuration (the
`config.bzl` files per package).
@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 Feb 16, 2020
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