Cretezy / redux-persist-expo-securestore

redux-persist storage for Expo's SecureStore
MIT License
74 stars 28 forks source link

Bump prettier from 1.18.2 to 2.0.5 #18

Open dependabot-preview[bot] opened 4 years ago

dependabot-preview[bot] commented 4 years ago

Bumps prettier from 1.18.2 to 2.0.5.

Release notes

Sourced from prettier's releases.

2.0.5

🔗 Changelog

2.0.4

🔗 Changelog

2.0.3

🔗 Changelog

2.0.2

🔗 Changelog

2.0.1

🔗 Changelog

2.0.0

diff

🔗 Release Notes

1.19.1

🔗 Changelog

Prettier 1.19: Long awaited Vue option, TypeScript 3.7 and new JavaScript features

🔗 Release Notes

Changelog

Sourced from prettier's changelog.

2.0.5

diff

Less: Fix formatting of :extend (#7984 by @fisker)

// Input
.class {
  &:extend(.some-class .some-other-class .some-very-loooooooooooooong-class all);
}

// Prettier 2.0.4 .class { &:extend( .some-class .some-other-class .some-very-loooooooooooooong-class all ); }

// Prettier 2.0.4 (Second format) .class { &: extend( .some-class .some-other-class .some-very-loooooooooooooong-class all ); }

// Prettier 2.0.5 .class { &:extend( .some-class .some-other-class .some-very-loooooooooooooong-class all ); }

Editor integration: Use resolve if builtin require.resolve is overridden (#8072 by @fisker)

This fixes issues that the users of Atom and WebStorm faced with 2.0.4.

Prettier now switches to using the resolve module for resolving configuration files and plugins if it detects that require.resolve isn't Node's builtin function (doesn't support the second argument), which happens in environments like editor extensions. To force the fallback, set the PRETTIER_FALLBACK_RESOLVE environment variable to true.

2.0.4

diff

Revert #7869, "[TypeScript] format TSAsExpression with same logic as BinaryExpression" (#7958)

2.0.3

diff

... (truncated)
Commits
Maintainer changes

This version was pushed to npm by thorn0, a new releaser for prettier since your current version.


Dependabot compatibility score

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 - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired)