Bump highcharts-export-server from 2.0.24 to 2.1.0 in /src

[dependabot[bot]]

Bumps highcharts-export-server from 2.0.24 to 2.1.0.

Changelog

Sourced from highcharts-export-server's changelog.

2.1.0

This version is not backwards compatible out of the box!

Breaking changes:

• Log destinations must now exist before starting file logging
• When running in server mode, the following options are now disabled by default:
  • callback
  • resources
  • customCode

Disabled options can be enabled by adding the --allowCodeExecution flag when starting the server. Using this flag is not recommended, and should not be done unless the server is sandboxed and not reachable on the public internet.

Changelog

• Added the --allowCodeExecution flag which is now required to be set when exporting pure JavaScript, using additional external resources, or using callback when running in server mode.
• Removed the mkdirp dependency
• SVG exporting will now block JavaScript entirely
• Added the navigationLocked flag to the Phantom page, which blocks e.g. <iframe> and page redirects.

2.0.30

• Fixed compatibility with mkdirp >=v1.0

2.0.29

• Added polyfill for DOMParser to accommodate Highcharts 9.0
• Updated some dependencies

2.0.28

• Fixed UUID and mkdirp versions in package.json

2.0.27

• Added venn module to build script

2.0.26

• Added coloraxis module to build script

2.0.25

• Fixed issue with optional scripts when using env variables to accept prompts

2.0.23

• Fixed issue with optional dependencies when installing headless

2.0.20-2.0.22

• Fixed pathing issue with NPM build when installing globally

2.0.19

• Added support for fetching sources through npm for automated builds. To use, set HIGHCHARTS_CDN to npm.
• Added support for pareto charts

... (truncated)

Commits

• See full diff in compare view

Maintainer changes

This version was pushed to npm by cvasseng, a new releaser for highcharts-export-server since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.