Skip to content

Allow --user-data-dir to be set in launcher properties#65

Merged
dignifiedquire merged 2 commits intokarma-runner:masterfrom
antigremlin:release/0.2
Jan 25, 2016
Merged

Allow --user-data-dir to be set in launcher properties#65
dignifiedquire merged 2 commits intokarma-runner:masterfrom
antigremlin:release/0.2

Conversation

@antigremlin
Copy link
Copy Markdown

Add a new chromeDataDir property to explicitly set the Chrome data
directory. Rationale:

Sometimes it is useful to run Chrome under Karma with certain plugins
loaded. One use-case is to have the JetBrains IDE Support plugin to
attach the IntelliJ debugger. We can do it with --load-extension but
this can also be prohibited by corporate policy. So one way to solve it
is to have the --user-data-dir point to a project subdirectory and to
install the plugin manually on the first run. It is preserved of course
on subsequent runs.

@googlebot
Copy link
Copy Markdown

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.


  • If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
  • If you signed the CLA as a corporation, please let us know the company's name.

@antigremlin
Copy link
Copy Markdown
Author

I signed it!

@googlebot
Copy link
Copy Markdown

CLAs look good, thanks!

@dignifiedquire
Copy link
Copy Markdown
Member

Thanks, can you change the commit message to follow our convention then I can merge it :)

Andrey Taranov added 2 commits December 17, 2015 15:13
Introduce a new parameter to custom launder properties: `chromeUserDir`
which allows to set the `--user-data-dir` command line option to point
to a specific place. Rationale:
Sometimes it is useful to run Chrome under Karma with certain plugins
loaded. One use-case is to have the **JetBrains IDE Support** plugin to
attach the IntelliJ debugger. We can do it with `--load-extension` but
this can also be prohibited by corporate policy. So one way to solve it
is to have the `--user-data-dir` point to a project subdirectory and to
install the plugin manually on the first run. It is preserved of course
on subsequent runs.
@antigremlin antigremlin changed the title Allow --user-data-dir to be set in custom launcher properties Allow --user-data-dir to be set in launcher properties Dec 17, 2015
@antigremlin
Copy link
Copy Markdown
Author

@dignifiedquire I think this you haven't noticed that the commit messages in this PR were corrected. Do you think you could merge this?

@dignifiedquire
Copy link
Copy Markdown
Member

Thanks :octocat: (yeah there are no notifications from github for pushes to PRs :( )

dignifiedquire added a commit that referenced this pull request Jan 25, 2016
Allow --user-data-dir to be set in launcher properties
@dignifiedquire dignifiedquire merged commit e3cc448 into karma-runner:master Jan 25, 2016
@nschipperbrainsmith
Copy link
Copy Markdown

@antigremlin @dignifiedquire The fix is not published on NPM i tried pulling it and found out that the modifications made to the index.js are not present within the package that is installed from NPM.

Which is problematic to say the least.

@dignifiedquire
Copy link
Copy Markdown
Member

New version is out

@nschipperbrainsmith
Copy link
Copy Markdown

A perfect thanks @dignifiedquire

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.

4 participants