Skip to content

Releases: simonw/shot-scraper

1.5

27 Sep 02:46
Compare
Choose a tag to compare
  • Several new features for the YAML configuration used by shot-scraper multi:
    • You can now add a - server: python -m http.server 8003 block to start a server running before screenshots are taken. The PID for this server will be recorded and the server automatically terminated when the command completes, unless you specify the --leave-server option in which case it will be left running, useful for debugging. #156
    • The sh: shell command or python: python code blocks can specify Python or shell commands to run before a screenshot is taken. This means a YAML script can make modifications to the environment in between screenshots, useful for things like progressive tutorials. #155
  • Fixed a bug that occurred if a max-width was accidentally applied to the <div> used for region screenshots. Thanks, Johann Klähn. #143
  • Documented that shot-scraper will quit with an error if a --wait-for expression has not resolved in 30s.

1.4

05 Feb 22:56
Compare
Choose a tag to compare
1.4
  • New --auth-username x --auth-password y options for each shot-scraper command, allowing a username and password to be set for HTTP Basic authentication. #140
  • shot-scraper URL --interactive mode now respects the -w and -h arguments setting the size of the browser viewport. Thanks, mhalle. #128
  • New --scale-factor option for setting scale factors other than 2 (for retina). Thanks, Niel Thiart. #136
  • New --browser-arg option for passing extra browser arguments (such as --browser-args "--font-render-hinting=none") through to the underlying browser. Thanks, Niel Thiart. #137

1.3

01 Nov 22:13
Compare
Choose a tag to compare
1.3
  • New --bypass-csp option for bypassing any Content Security Policy on the page that prevents executing further JavaScript. Thanks, Brenton Cleeland. #116
  • Screenshots taken using shot-scraper --interactive $URL - which allows you to interact with the page in a browser window and then hit <enter> to take the screenshot - it no longer reloads the page before taking the shot (which ignored your activity). #125
  • Improved accessibility of documentation. Thanks, Paolo Melchiorre. #120

1.2

27 Apr 03:03
Compare
Choose a tag to compare
1.2
  • New --omit-background option to the shot command to optionally create transparent PNGs. Thanks, Ben Welsh. #108
  • Fixed bug that caused shot-scraper to fail to take screenshots on Windows. Thanks, Omer Rosenbaum. #104
  • New --silent option for the shot, multi, pdf and html commands, to disable the default console output. #107

Full documentation: https://shot-scraper.datasette.io/

1.1.1

30 Jan 02:34
Compare
Choose a tag to compare
  • Deprecated the shot-scraper multi --fail-on-error option in favor of the new --fail option. --fail-on-error will continue to work until shot-scraper 2.0 (should that ever be released), but is no longer displayed in the --help menu or documentation. #103

1.1

30 Jan 00:57
Compare
Choose a tag to compare
1.1
  • New --log-console option for logging the output of calls to console.log() to standard error. #101
  • New --skip and --fail options to specify what should happen if an HTTP 4xx or 5xx error is encountered while trying to load the page. --skip will ignore the error and either exit cleanly or move on to the next screenshot (in the case of multi). --fail will cause the tool to return a non-zero exit code, useful for running in CI environments. #102

1.0.1

24 Oct 23:07
88fc54b
Compare
Choose a tag to compare

1.0

15 Oct 19:46
Compare
Choose a tag to compare
1.0

0.17

14 Oct 19:32
dc590e8
Compare
Choose a tag to compare
  • New shot-scraper multi -o option for specifying a subset of one or more output files to execute that are defined in the YAML. This is useful for testing a larger shots.yml file without re-taking every screenshot every time the command is run. #94

0.16

15 Sep 03:18
955bbc9
Compare
Choose a tag to compare
  • Fixed error message displayed when attempting to use --log-requests on a page that includes a redirect. #90
  • --log-requests output now includes a "status": 200 field indicating the HTTP status code returned by that response.