custom-elements-everywhere
custom-elements-everywhere copied to clipboard
Update dependency wireit to ^0.9.0
This PR contains the following updates:
Package | Change | Age | Adoption | Passing | Confidence |
---|---|---|---|---|---|
wireit | ^0.7.1 -> ^0.9.0 |
Release Notes
google/wireit
v0.9.0
Changed
-
[BREAKING] A
watch
argument (without the--
) is now passed to the script, instead of erroring, to make it consistent with all other arguments. (The error was previously repoted to aid in migration fromwatch
to--watch
, which changed in `v0.6.0). -
[BREAKING] The
.yarn/
folder has been added to the list of default excluded paths. -
It is now allowed to set the value of a wireit script to e.g.
"../node_modules/.bin/wireit"
if you need to directly reference a wireit binary in a specific location. -
yarn.lock
andpnpm-lock.yaml
are now automatically used as package lock files when yarn and pnpm are detected, respectively. (Previouslypackage-lock.json
was always used unless thepackageLocks
array was manually set).
Fixed
- The
--watch
flag can now be passed to chained scripts when using yarn 1.x. However duehttps://github.com/yarnpkg/yarn/issues/89058905, extra arguments passed after a--
are still not supported with yarn 1.x. Please consider upgrading to yarn 3.x, or switching to npm.
v0.8.0
Added
-
[BREAKING] The following folders are now excluded by default from both the
files
andoutput
arrays:-
.git/
-
.hg/
-
.svn/
-
.wireit/
-
CVS/
-
node_modules/
In the highly unusual case that you need to reference a file in one of those folders, set
allowUsuallyExcludedPaths: true
to remove all default excludes. -
Fixed
-
Fixed
Invalid string length
andheap out of memory
errors when writing the fingerprint files for large script graphs. -
Fixed bug where an exclude pattern for a folder with a trailing slash would not be applied (e.g.
!foo
worked but!foo/
did not).
v0.7.3
Added
-
Added
"service": true
setting, which is well suited for long-running processes like servers. A service is started either when it is invoked directly, or when another script that depends on it is ready to run. A service is stopped when all scripts that depend on it have finished, or when Wireit is exited. -
Added
"cascade": false
setting to dependencies.By default, the fingerprint of a script includes the fingerprints of its dependencies. This means a script will re-run whenever one of its dependencies re-runs, even if the output produced by the dependency didn't actually change.
Now, if a dependency is annotated with
"cascade": false
, then the fingerprint of that dependency will no longer be included in the script's own fingerprint. This means a script won't neccessarily re-run just because a dependency re-ran — though Wireit will still always run the dependency first if it is not up-to-date.Using
"cascade": false
can result in faster builds thanks to fewer re-runs, but it is very important to specify all of the input files generated by the dependency which the script depends on in thefiles
array.Example:
{ "wireit": { "build": { "command": "tsc", "files": ["tsconfig.json", "src/**/*.ts"], "output": "lib/**", }, "bundle": { "command": "rollup -c", "files": ["rollup.config.json", "lib/**/*.js", "!lib/test"], "output": "dist/bundle.js", "dependencies": { [ "script": "build", "cascade": false ] } } } }
Changed
- Added string length > 0 requirement to the
command
,dependencies
,files
,output
, andpackageLocks
properties inschema.json
.
Fixed
-
Fixed memory leak in watch mode.
-
Added graceful recovery from
ECONNRESET
and other connection errors when using GitHub Actions caching. -
Fixed bug where a leading slash on a
files
oroutput
path was incorrectly interpreted as relative to the filesystem root, instead of relative to the package, in watch mode.
v0.7.2
Fixed
- Fixed issue where a redundant extra run could be triggered in watch mode when multiple scripts were watching the same file(s).
Changed
-
stdout color output is now forced when Wireit is run with a text terminal attached.
-
Default number of scripts run in parallel is now 2x logical CPU cores instead of 4x.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
- [ ] If you want to rebase/retry this PR, check this box
This PR has been generated by Mend Renovate. View repository job log here.