Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ impro (~0.8.0 → ~0.9.0) · Repo
Commits
See the full diff on Github. The new version differs by 20 commits:
0.9.0
Bump timeout in an attempt to fix CI.
Amend test warmup code for on macOS so no UI opens with inkscape v1+.
Differentiate between test files and utility code after 7321c59.
Switch to GitHub Actions
Support avif
prettier --write '**/*.{js,json,md}'
Add missing stuff to .prettierignore
Also use prettier for *.json and *.md
Update prettier to ~2.2.1
for f in $(find src test -name '*.js'); do lebab --transform for-of,arg-rest,arg-spread,arrow,arrow-return,let --replace $f ; done
npm i --save-dev eslint-plugin-promise
npm i --save-dev eslint@latest eslint-config-{prettier,standard} eslint-plugin-{import,node,prettier,standard}@latest eslint-plugin-mocha@7
npm uninstall eslint-config-pretty-standard
Switch to a json-based eslint config
Fix duplicate require
Move the unexpected setup to a separate file
Fix typo in test description
Update mocha to ^8.2.1, switch to .mocharc.json
Update sharp to ~0.27.0
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.All Depfu comment commands