Skip to content

fix: integration-browser should work from npm #127

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
merged 1 commit into from
Jul 8, 2019

Conversation

seebees
Copy link
Contributor

@seebees seebees commented Jun 24, 2019

Integration-browser should be able to be installed from npm
and just work.

  • include karma.config.js in package
  • karma and friends are dependencies, not a devDependencies
  • webpack the js files, not the typescript files

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Integration-browser should be able to be installed from npm
and just work.

* include karma.config.js in package
* karma and friends are dependencies, not a devDependencies
* webpack the js files, not the typescript files
@seebees seebees requested a review from a team July 2, 2019 18:07
Copy link

@lizroth lizroth left a comment

Choose a reason for hiding this comment

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

I'm lizroth and I approve this pile of JSON.

@seebees seebees merged commit 334c130 into aws:master Jul 8, 2019
@seebees seebees deleted the portable-integration-browser branch July 8, 2019 19:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants