-
Notifications
You must be signed in to change notification settings - Fork 124
Comparing changes
Open a pull request
base repository: karma-runner/karma-chrome-launcher
base: v0.2.1
head repository: karma-runner/karma-chrome-launcher
compare: v0.2.3
- 16 commits
- 4 files changed
- 4 contributors
Commits on Dec 1, 2015
-
Configuration menu - View commit details
-
Copy full SHA for 426e7c3 - Browse repository at this point
Copy the full SHA 426e7c3View commit details -
Configuration menu - View commit details
-
Copy full SHA for ed24321 - Browse repository at this point
Copy the full SHA ed24321View commit details -
Configuration menu - View commit details
-
Copy full SHA for c4b08b9 - Browse repository at this point
Copy the full SHA c4b08b9View commit details -
Configuration menu - View commit details
-
Copy full SHA for 8b7dbf5 - Browse repository at this point
Copy the full SHA 8b7dbf5View commit details -
Configuration menu - View commit details
-
Copy full SHA for b217497 - Browse repository at this point
Copy the full SHA b217497View commit details -
Configuration menu - View commit details
-
Copy full SHA for b11effd - Browse repository at this point
Copy the full SHA b11effdView commit details -
Configuration menu - View commit details
-
Copy full SHA for 153ba3f - Browse repository at this point
Copy the full SHA 153ba3fView commit details -
Configuration menu - View commit details
-
Copy full SHA for b30c40c - Browse repository at this point
Copy the full SHA b30c40cView commit details -
Merge branch 'master' of https://github.com/karma-runner/karma-chrome…
Configuration menu - View commit details
-
Copy full SHA for 1bcf4b8 - Browse repository at this point
Copy the full SHA 1bcf4b8View commit details
Commits on Dec 17, 2015
-
feat(config): Allow --user-data-dir to be set in launcher properties
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.
Andrey Taranov committedDec 17, 2015 Configuration menu - View commit details
-
Copy full SHA for 2c0b7f4 - Browse repository at this point
Copy the full SHA 2c0b7f4View commit details -
docs(config): Document
chromeDataDirproperty for custom launchersAndrey Taranov committedDec 17, 2015 Configuration menu - View commit details
-
Copy full SHA for 72d8de4 - Browse repository at this point
Copy the full SHA 72d8de4View commit details
Commits on Jan 6, 2016
-
Configuration menu - View commit details
-
Copy full SHA for 600e1b6 - Browse repository at this point
Copy the full SHA 600e1b6View commit details -
Merge pull request #66 from Florian-R/fix-group-permission
chore: update which
Configuration menu - View commit details
-
Copy full SHA for c8f1a64 - Browse repository at this point
Copy the full SHA c8f1a64View commit details
Commits on Jan 25, 2016
-
Merge pull request #65 from antigremlin/release/0.2
Allow --user-data-dir to be set in launcher properties
Configuration menu - View commit details
-
Copy full SHA for e3cc448 - Browse repository at this point
Copy the full SHA e3cc448View commit details
Commits on Mar 22, 2016
-
Configuration menu - View commit details
-
Copy full SHA for f08fa14 - Browse repository at this point
Copy the full SHA f08fa14View commit details -
Configuration menu - View commit details
-
Copy full SHA for 7a3d127 - Browse repository at this point
Copy the full SHA 7a3d127View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v0.2.1...v0.2.3