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.
This PR contains the following updates:
16.3.1
->16.4.5
8.0.3
->9.0.11
4.1.5
->5.0.0
3.1.0
->3.3.0
3.1.3
->4.0.0
^15.0.0
->^16.0.0
34.0.0
->36.0.0
This is a special PR that replaces
npm-run-all
with the community suggested minimal stable replacement version.Release Notes
motdotla/dotenv (dotenv)
v16.4.5
Compare Source
Changed
path
option. return to historical behavior: do not attempt to auto find.env
ifpath
set. (regression was introduced in16.4.3
) #814v16.4.4
Compare Source
Changed
?.
with old school&&
(fixing node 12 failures) #812v16.4.3
Compare Source
Changed
options.path
#805v16.4.2
Compare Source
Changed
dotenvx.com
v16.4.1
Compare Source
path
option #797v16.4.0
Compare Source
error.code
to error messages around.env.vault
decryption handling #795.env.vault
file when filename(s) passed as an array #784v16.3.2
Compare Source
Added
Changed
populate
#792typicode/husky (husky)
v9.0.11
Compare Source
v9.0.10
Compare Source
v9.0.9
Compare Source
v9.0.8
Compare Source
v9.0.7
Compare Source
~/.huskyrc
correctly (compatibility with v8)v9.0.6
Compare Source
v9.0.5
Compare Source
v9.0.4
Compare Source
v9.0.3
Compare Source
v9.0.2
Compare Source
What's Changed
New Contributors
Full Changelog: typicode/husky@v9.0.1...v9.0.2
v9.0.1
Compare Source
Kicking off the year with an exciting update!
TLDR;
Improved user experience and a (even) smaller package size while packing in more features!
👋 By the Way
I'm available for remote work (Front-end/Back-end mainly JS/TS but open to other stacks Rails, Go, Elixir). You can contact me at my mail: typicode at gmail 🙂
Introducing
husky init
Adding husky to a project is now easier than ever. Although the installation process was straightforward, it often required consulting the documentation.
v8
v9
Adding a New Hook
Adding a hook is now as simple as creating a file. This can be accomplished using your favorite editor, a script or a basic
echo
command.v8
v9
Further Size Reduction
v8
was already the most compact Git hooks manager at approximately6kB
.v9
takes this a step further, reducing the size to just3kB
, likely making it the smallest devDependency in your toolkit.To give you an idea of how small it is, the biggest file in the project is the MIT license 😄
More to Come
Additional features are in the pipeline for
v9
. Stay tuned 🙌Other Changes
--provenance
for safer publishing.$XDG_CONFIG_HOME
support. Move~/.huskyrc
to~/.config/husky/init.sh
for centralized configuration.husky install
. Usehusky
orhusky some/dir
for the same functionality (deprecation notice to be added)..git
is missing; it now triggers a warning instead of failure.HUSKY_DEBUG=1
withHUSKY=2
for debugging.ESM
for module usage.How to Migrate
v9
is backward compatible withv8
, allowing you to freely upgrade and migrate your hooks later.package.json
.husky/pre-commit
prettier/prettier (prettier)
v3.3.0
Compare Source
diff
🔗 Release Notes
v3.2.5
Compare Source
diff
Support Angular inline styles as single template literal (#15968 by @sosukesuzuki)
Angular v17 supports single string inline styles.
Unexpected embedded formatting for Angular template (#15969 by @JounQin)
Computed template should not be considered as Angular component template
Use
"json"
parser fortsconfig.json
by default (#16012 by @sosukesuzuki)In v2.3.0, we introduced
"jsonc"
parser which adds trialing comma by default.When adding a new parser we also define how it will be used based on the
linguist-languages
data.tsconfig.json
is a special file used by TypeScript, it uses.json
file extension, but it actually uses the JSON with Comments syntax. However, we found that there are many third-party tools not recognize it correctly because of the confusing.json
file extension.We decide to treat it as a JSON file for now to avoid the extra configuration step.
To keep using the
"jsonc"
parser for yourtsconfig.json
files, add the following to your.pretterrc
filev3.2.4
Compare Source
diff
Fix incorrect parser inference (#15947 by @fisker)
Files like
.eslintrc.json
were incorrectly formatted as JSONC files.v3.2.3
Compare Source
diff
Throw errors for invalid code (#15881 by @fisker, @Josh-Cena, @auvred)
Fix parser inference (#15927 by @fisker)
v3.2.2
Compare Source
diff
Fix crash when parsing template literal CSS in a JSX style tag using a spread attribute (#15896 by @eelco)
For example this code would crash before:
Fix formatting error on optional call expression and member chain (#15920 by @sosukesuzuki)
v3.2.1
Compare Source
diff
Fix formatting error on member chain (#15915 by @sosukesuzuki)
v3.2.0
Compare Source
diff
🔗 Release Notes
v3.1.1
Compare Source
diff
Fix config file search (#15363 by @fisker)
Previously, we start search for config files from the filePath as a directory, if it happened to be a directory and contains config file, it will be used by mistake.
Skip explicitly passed symbolic links with
--no-error-on-unmatched-pattern
(#15533 by @sanmai-NL)Since Prettier v3, we stopped following symbolic links, however in some use cases, the symbolic link patterns can't be filtered out, and there is no way to prevent Prettier from throwing errors.
In Prettier 3.1.1, you can use
--no-error-on-unmatched-pattern
to simply skip symbolic links.Consistently use tabs in ternaries when
useTabs
istrue
(#15662 by @auvred)Improve config file search (#15663 by @fisker)
The Prettier config file search performance has been improved by more effective cache strategy.
Fix unstable and ugly formatting for comments in destructuring patterns (#15708 by @sosukesuzuki)
Support "Import Attributes" (#15718 by @fisker)
TypeScript 5.3 supports the latest updates to the import attributes proposal.
Fix false claim in docs that cursorOffset is incompatible with rangeStart/rangeEnd (#15750 by @ExplodingCabbage)
The cursorOffset option has in fact been compatible with rangeStart/rangeEnd for over 5 years, thanks to work by @ds300. However, Prettier's documentation (including the CLI
--help
text) continued to claim otherwise, falsely. The documentation is now fixed.Keep curly braces and
from
keyword in emptyimport
statements (#15756 by @fisker)Keep empty import attributes and assertions (#15757 by @fisker)
prettier/pretty-quick (pretty-quick)
v4.0.0
Compare Source
Major Changes
f1cacb2
Thanks @JounQin! - feat!: support prettier v3v3.3.1
Compare Source
Patch Changes
ca4d269
Thanks @JounQin! - fix: remove unexpected .tsbuildinfo filev3.3.0
Compare Source
Minor Changes
93924ab
Thanks @SukkaW! - refactor: replacechalk
andmultimatch
with their lightweight and performant alternativesPatch Changes
71aab56
Thanks @JounQin! - fix: more robust computation of git directoryv3.2.1
Compare Source
Patch Changes
1929cc9
Thanks @JounQin! - fix: add tslib as dependencyv3.2.0
Compare Source
Minor Changes
4f5a345
Thanks @JounQin! - feat: migrate code base to TypeScriptv3.1.4
Compare Source
Patch Changes
49acad2
Thanks @JounQin! - fix: incorrect prettier peer versionstylelint/stylelint (stylelint)
v16.6.1
Compare Source
no-descending-specificity
false positives for nested selectors (#7724) (@romainmenke).selector-type-no-unknown
false positive formodel
(#7718) (@Mouvedia).v16.6.0
Compare Source
function-calc-no-unspaced-operator
false negatives (#7655 & #7670 & #7676) (@ybiquitous & @romainmenke).selector-not-notation
autofix of the"simple"
option (#7703) (@Mouvedia).selector-max-specificity
end positions (#7685) (@romainmenke).no-descending-specificity
end positions (#7701) (@romainmenke).npm fund
(#7707) (@ybiquitous).v16.5.0
Compare Source
ignoreValues
forvalue-no-vendor-prefix
(#7650) (@Mouvedia).shorthand-property-no-redundant-values
false negatives for functions (#7657) (@ybiquitous).value-no-vendor-prefix
false negatives/positives (#7654 & #7658) (@Mouvedia).CosmiconfigResult
type error (#7661) (@ybiquitous).v16.4.0
Compare Source
no-unknown-custom-media
(#7594) (@fpetrakov).ignoreLonghands: []
todeclaration-block-no-redundant-longhand-properties
(#7611) (@Mouvedia).ignore: ["keyframe-selectors"]
torule-selector-property-disallowed-list
(#7572) (@emmacharp).declaration-block-no-redundant-longhand-properties
autofix conflicts (#7626) (@Mouvedia).declaration-block-no-redundant-longhand-properties
autofix fortext-decoration
(#7611) (@Mouvedia).declaration-block-no-shorthand-property-overrides
false negatives forborder
(#7585) (@fpetrakov).declaration-block-no-shorthand-property-overrides
false negatives forfont
andborder
(#7606) (@Mouvedia).function-calc-no-unspaced-operator
false negatives for some math functions (#7619) (@Mouvedia).function-no-unknown
false positives foranchor
andanchor-size
(#7607) (@Mouvedia).selector-max-attribute
end positions (#7592) (@romainmenke).selector-max-class
end positions (#7590) (@romainmenke).selector-max-combinators
end positions (#7596) (@romainmenke).selector-max-compound-selectors
end positions (#7599) (@romainmenke).selector-max-pseudo-class
end positions (#7598) (@romainmenke).selector-max-universal
end positions (#7597) (@romainmenke).selector-type-no-unknown
false positives for experimental and deprecated HTML tags (#7612) (@Mouvedia).v16.3.1
Compare Source
selector-max-id
end positions (#7571) (@romainmenke)./index.js
(#7578) (@ota-meshi).v16.3.0
Compare Source
ignoreSelectors: []
toselector-max-compound-selectors
(#7544) (@FloEdelmann).string
andverbose
formatters (#7539) (@m-allanson).*-deprecation
command-line flags of Node.js (#7550) (@fpetrakov).rule-selector-property-disallowed-list
false positives for nesting selectors (#7558) (@romainmenke).selector-pseudo-*-allowed-list
false positives for vendor prefixes (#7525) (@carlosjeurissen).report()
forindex
/endIndex
zero values (#7565) (@romainmenke).selector-max-type
end positions (#7518) (@romainmenke).v16.2.1
Compare Source
custom-property-no-missing-var-function
false positives for properties that can contain author-defined identifiers (#7478) (@ybiquitous).selector-pseudo-class-no-unknown
false positives for:seeking
, the media loading state and sound state pseudo-classes (#7490) (@Mouvedia).selector-max-specificity
false positives withignoreSelectors
option forof <selector>
syntax (#7475) (@ybiquitous).function-calc-no-unspaced-operator
performance (#7505) (@ybiquitous).validateOptions
to report when secondary option object is an empty object or null (#7476) (@ybiquitous).report()
error message responsibility for a missing node or line number (#7474) (@ybiquitous).v16.2.0
Compare Source
media-query-no-invalid
specific problem messages (#7462) (@romainmenke).checkContextFunctionalPseudoClasses: []
toselector-max-id
(#7380) (@brigitamaria).declaration-property-value-no-unknown
false negatives for@starting-style
(#7461) (@fpetrakov).function-no-unknown|value-keyword-case
false positives for template literals with line breaks (#7443) (@Sh031224).allowEmptyInput
option ignored in configuration object regression (#7446) (@ybiquitous).at-rule-no-unknown
false positives for@starting-style
(#7438) (@fpetrakov).ERR_UNSUPPORTED_ESM_URL_SCHEME
for--custom-formatter
on Windows (#7432) (@JounQin).Error: Could not find <package>
message clarity (#7456) (@jeddy3).overrides.files
negated pattern regression introduced in 15.0.0 (#7468) (@ybiquitous).v16.1.0
Compare Source
lightness-notation
rule (#7366) (@fpetrakov).ignore: ["keyframe-selectors"]
toselector-disallowed-list
(#7417) (@mattxwang).selector-pseudo-class-no-unknown
false positive for:popover-open
(#7425) (@mattxwang).declaration-property-value-no-unknown
and other false positives for multiline SCSS interpolation. (#7406) (@FloEdelmann).function-url-quotes
false positives for SCSS variable and@
character (#7416) (@mattxwang).v16.0.2
Compare Source
ERR_UNSUPPORTED_ESM_URL_SCHEME
error on Windows (#7383) (@JounQin).v16.0.1
Compare Source
v16.0.0
Compare Source
Migrating to
16.0.0
guide.stylelint.formatters
object to havePromise
values (#7184) (@ybiquitous).fix
regardless of extension (#7357) (@ybiquitous).stylelint.rules
object to havePromise
values (#7279) (@ybiquitous).stylelint.utils.checkAgainstRule
to be an async function (#7339) (@ybiquitous).output
property in a Node.js API returned object. Instead,report
/code
properties are recommended (#7183) (@ybiquitous) & (@haocheng6).exports
field topackage.json
for Conditional Exports (ESM/CommonJS) (#7307) (@ybiquitous).severity
secondary option's function support (#7202) (@kizu).Promise
formatter function (#7184) (@ybiquitous).report
/code
properties to a Node.js API returned object (#7183) (@ybiquitous) & (@haocheng6)..js
extension to.mjs
and.cjs
(#7307) (@ybiquitous).stylelint/stylelint-config-standard (stylelint-config-standard)
v36.0.0
Compare Source
stylelint
less than16.1.0
from peer dependencies.lightness-notation: "percentage"
rule.v35.0.0
Compare Source
stylelint
less than16.0.0
from peer dependencies.18.12.0
support.stylelint-config-recommended@14.0.0
.Configuration
📅 Schedule: Branch creation - "before 4am on Monday" in timezone America/New_York, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate. View repository job log here.