Skip to content

Update all #10

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
Aug 2, 2021
Merged

Update all #10

merged 1 commit into from
Aug 2, 2021

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Aug 2, 2021

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@ampproject/worker-dom 0.29.3 -> 0.30.1 age adoption passing confidence
@types/parse5 6.0.0 -> 6.0.1 age adoption passing confidence
chai (source) 4.2.0 -> 4.3.4 age adoption passing confidence
chrome-launcher ^0.13.4 -> 0.14.0 age adoption passing confidence
esbuild 0.12.8 -> 0.12.17 age adoption passing confidence
globby 11.0.3 -> 11.0.4 age adoption passing confidence
lighthouse ^7.2.0 -> 7.5.0 age adoption passing confidence
mocha (source) 8.2.1 -> 8.4.0 age adoption passing confidence
prettier (source) 2.3.1 -> 2.3.2 age adoption passing confidence
typescript (source) 4.3.2 -> 4.3.5 age adoption passing confidence

Release Notes

ampproject/worker-dom

v0.30.1

Compare Source

v0.30.0

Compare Source

chaijs/chai

v4.3.4

Compare Source

This fixes broken inspect behavior with bigints (#​1321) (#​1383) thanks @​vapier

v4.3.3

Compare Source

This reintroduces Assertion as an export in the mjs file. See chaijs/chai#1378 & chaijs/chai#1375

v4.3.2

Compare Source

This fixes a regression in IE11. See chaijs/chai#1380 & chaijs/chai#1379

v4.3.1

Compare Source

This releases fixed an engine incompatibility with 4.3.0

The 4.x.x series of releases will be compatible with Node 4.0. Please report any errors found in Node 4 as bugs, and they will be fixed.

The 5.x.x series, when released, will drop support for Node 4.0

This fix also ensures pathval is updated to 1.1.1 to fix CVE-2020-7751

v4.3.0

Compare Source

This is a minor release.

Not many changes have got in since the last release but this one contains a very important change (#​1257) which will allow jest users to get better diffs. From this release onwards, jest users will be able to see which operator was used in their diffs. The operator is a property of the AssertionError thrown when assertions fail. This flag indicates what kind of comparison was made.

This is also an important change for plugin maintainers. Plugin maintainers will now have access to the operator flag, which they can have access to through an utilmethod calledgetOperator`.

Thanks to all the amazing people that contributed to this release.

New Features

  • Allow contain.oneOf to take an array of possible values (@​voliva)
  • Adding operator attribute to assertion error (#​1257) (@​rpgeeganage)
  • The closeTo error message will now inform the user when a delta is required (@​eouw0o83hf)

Docs

  • Add contains flag to oneOf documentation (@​voliva)

Tests

Chores

GoogleChrome/chrome-launcher

v0.14.0

Compare Source

  • ac1f4aff move to minimum node 12; remove rimraf (#​237)
  • dec646c4 deps: remove mkdirp for fs.mkdirSync (#​234)
  • 83ab178a update minimum node version (#​222)
  • a5f6eb2f add additional chrome flags (#​227)
  • 3a7c9610 reword unset-CHROME_PATH error message
  • b1b8dc74 rename disabled TranslateUI to Translate to match Chrome (#​225)
  • beb41360 chore: update dependencies and test targets (#​221)
  • df9d564a tests: migrate from travis to github actions (#​228)
  • 673da08b tests: add mac/win bots to ci (#​232)
  • a700ae0c docs: fix readme's getInstallations() section (#​212)
  • chrome-flags-for-tools.md update
    • 4b98587d massive update and refactor (#​226)
    • e45b100f minor tweaks to headless and others
    • 3a90c21b fix links
    • 8429ca93 add feature flags description
    • 21db5f9f even more documented flags (#​231)
evanw/esbuild

v0.12.17

Compare Source

  • Fix a bug with private fields and logical assignment operators (#​1418)

    This release fixes a bug where code using private fields in combination with logical assignment operators was transformed incorrectly if the target environment supported logical assignment operators but not private fields. Since logical assignment operators are assignment operators, the entire operator must be transformed even if the operator is supported. This should now work correctly:

    // Original code
class Foo {
  #x
  foo() {
    this.#x &&= 2
    this.#x ||= 2
    this.#x ??= 2
  }
}

// Old output
var _x;
class Foo {
  constructor() {
    __privateAdd(this, _x, void 0);
  }
  foo() {
    this._x &&= 2;
    this._x ||= 2;
    this._x ??= 2;
  }
}
_x = new WeakMap();

// New output
var _x, _a;
class Foo {
  constructor() {
    __privateAdd(this, _x, void 0);
  }
  foo() {
    __privateGet(this, _x) && __privateSet(this, _x, 2);
    __privateGet(this, _x) || __privateSet(this, _x, 2);
    __privateGet(this, _x) ?? __privateSet(this, _x, 2);
  }
}
_x = new WeakMap();

  • Fix a hoisting bug in the bundler (#​1455)

    This release fixes a bug where variables declared using var inside of top-level for loop initializers were not hoisted inside lazily-initialized ES modules (such as those that are generated when bundling code that loads an ES module using require). This meant that hoisted function declarations incorrectly didn't have access to these loop variables:

    // entry.js
console.log(require('./esm-file').test())

// esm-file.js
for (var i = 0; i < 10; i++) ;
export function test() { return i }

    Old output (incorrect):

    // esm-file.js
var esm_file_exports = {};
__export(esm_file_exports, {
  test: () => test
});
function test() {
  return i;
}
var init_esm_file = __esm({
  "esm-file.js"() {
    for (var i = 0; i < 10; i++)
      ;
  }
});

// entry.js
console.log((init_esm_file(), esm_file_exports).test());

    New output (correct):

    // esm-file.js
var esm_file_exports = {};
__export(esm_file_exports, {
  test: () => test
});
function test() {
  return i;
}
var i;
var init_esm_file = __esm({
  "esm-file.js"() {
    for (i = 0; i < 10; i++)
      ;
  }
});

// entry.js
console.log((init_esm_file(), esm_file_exports).test());

  • Fix a code generation bug for private methods (#​1424)

    This release fixes a bug where when private methods are transformed and the target environment is one that supports private methods (such as esnext), the member function name was uninitialized and took on the zero value by default. This resulted in the member function name becoming __create instead of the correct name since that's the name of the symbol at index 0. Now esbuild always generates a private method symbol even when private methods are supported, so this is no longer an issue:

    // Original code
class Foo {
  #a() { return 'a' }
  #b() { return 'b' }
  static c
}

// Old output
var _a, __create, _b, __create;
var Foo = class {
  constructor() {
    __privateAdd(this, _a);
    __privateAdd(this, _b);
  }
};
_a = new WeakSet();
__create = function() {
  return "a";
};
_b = new WeakSet();
__create = function() {
  return "b";
};
__publicField(Foo, "c");

// New output
var _a, a_fn, _b, b_fn;
var Foo = class {
  constructor() {
    __privateAdd(this, _a);
    __privateAdd(this, _b);
  }
};
_a = new WeakSet();
a_fn = function() {
  return "a";
};
_b = new WeakSet();
b_fn = function() {
  return "b";
};
__publicField(Foo, "c");

  • The CLI now stops watch and serve mode when stdin is closed (#​1449)

    To facilitate esbuild being called from the Erlang VM, esbuild's command-line interface will now exit when in --watch or --serve mode if stdin is closed. This change is necessary because the Erlang VM doesn't have an API for terminating a child process, so it instead closes stdin to indicate that the process is no longer needed.

    Note that this only happens when stdin is not a TTY (i.e. only when the CLI is being used non-interactively) to avoid disrupting the use case of manually moving esbuild to a background job using a Unix terminal.

    This change was contributed by @​josevalim.

v0.12.16

Compare Source

  • Remove warning about bad CSS @-rules (#​1426)

    The CSS bundler built in to esbuild is only designed with real CSS in mind. Running other languages that compile down to CSS through esbuild without compiling them down to CSS first can be a bad idea since esbuild applies browser-style error recovery to invalid syntax and uses browser-style import order that other languages might not be expecting. This is why esbuild previously generated warnings when it encountered unknown CSS @-rules.

    However, some people want to run other non-CSS languages through esbuild's CSS bundler anyway. So with this release, esbuild will no longer generate any warnings if you do this. But keep in mind that doing this is still potentially unsafe. Depending on the input language, using esbuild's CSS bundler to bundle non-CSS code can still potentially alter the semantics of your code.

  • Allow ES2021 in tsconfig.json (#​1470)

    TypeScript recently added support for ES2021 in tsconfig.json so esbuild now supports this too. This has the same effect as if you passed --target=es2021 to esbuild. Keep in mind that the value of target in tsconfig.json is only respected if you did not pass a --target= value to esbuild.

  • Avoid using the worker_threads optimization in certain old node versions (#​1462)

    The worker_threads optimization makes esbuild's synchronous API calls go much faster than they would otherwise. However, it turns out this optimization cannot be used in certain node versions older than v12.17.0, where node throws an error when trying to create the worker. This optimization is now disabled in these scenarios.

    Note that these old node versions are currently in maintenance. I recommend upgrading to a modern version of node if run-time performance is important to you.

  • Paths starting with node: are implicitly external when bundling for node (#​1466)

    This replicates a new node feature where you can prefix an import path with node: to load a native node module by that name (such as import fs from "node:fs/promises"). These paths also have special behavior:

    Core modules can also be identified using the node: prefix, in which case it bypasses the require cache. For instance, require('node:http') will always return the built in HTTP module, even if there is require.cache entry by that name.

    With this release, esbuild's built-in resolver will now automatically consider all import paths starting with node: as external. This new behavior is only active when the current platform is set to node such as with --platform=node. If you need to customize this behavior, you can write a plugin to intercept these paths and treat them differently.

  • Consider \ and / to be the same in file paths (#​1459)

    On Windows, there are many different file paths that can refer to the same underlying file. Windows uses a case-insensitive file system so for example foo.js and Foo.js are the same file. When bundling, esbuild needs to treat both of these paths as the same to avoid incorrectly bundling the file twice. This is case is already handled by identifying files by their lower-case file path.

    The case that wasn't being handled is the fact that Windows supports two different path separators, / and \, both of which mean the same thing. For example foo/bar.js and foo\bar.js are the same file. With this release, this case is also handled by esbuild. Files that are imported in multiple places with inconsistent path separators will now be considered the same file instead of bundling the file multiple times.

v0.12.15

Compare Source

  • Fix a bug with var() in CSS color lowering (#​1421)

    This release fixes a bug with esbuild's handling of the rgb and hsl color functions when they contain var(). Each var() token sequence can be substituted for any number of tokens including zero or more than one, but previously esbuild's output was only correct if each var() inside of rgb or hsl contained exactly one token. With this release, esbuild will now not attempt to transform newer CSS color syntax to older CSS color syntax if it contains var():

    /* Original code */
a {
  color: hsl(var(--hs), var(--l));
}

/* Old output */
a {
  color: hsl(var(--hs), ,, var(--l));
}

/* New output */
a {
  color: hsl(var(--hs), var(--l));
}

    The bug with the old output above happened because esbuild considered the arguments to hsl as matching the pattern hsl(h s l) which is the new space-separated form allowed by CSS Color Module Level 4. Then esbuild tried to convert this to the form hsl(h, s, l) which is more widely supported by older browsers. But this substitution doesn't work in the presence of var(), so it has now been disabled in that case.

v0.12.14

Compare Source

  • Fix the file loader with custom namespaces (#​1404)

    This fixes a regression from version 0.12.12 where using a plugin to load an input file with the file loader in a custom namespace caused esbuild to write the contents of that input file to the path associated with that namespace instead of to a path inside of the output directory. With this release, the file loader should now always copy the file somewhere inside of the output directory.

v0.12.13

Compare Source

  • Fix using JS synchronous API from from non-main threads (#​1406)

    This release fixes an issue with the new implementation of the synchronous JS API calls (transformSync and buildSync) when they are used from a thread other than the main thread. The problem happened because esbuild's new implementation uses node's worker_threads library internally and non-main threads were incorrectly assumed to be esbuild's internal thread instead of potentially another unrelated thread. Now esbuild's synchronous JS APIs should work correctly when called from non-main threads.

v0.12.12

Compare Source

  • Fix file loader import paths when subdirectories are present (#​1044)

    Using the file loader for a file type causes importing affected files to copy the file into the output directory and to embed the path to the copied file into the code that imported it. However, esbuild previously always embedded the path relative to the output directory itself. This is problematic when the importing code is generated within a subdirectory inside the output directory, since then the relative path is wrong. For example:

    $ cat src/example/entry.css
div {
  background: url(../images/image.png);
}

$ esbuild --bundle src/example/entry.css --outdir=out --outbase=src --loader:.png=file

$ find out -type f
out/example/entry.css
out/image-55DNWN2R.png

$ cat out/example/entry.css
/* src/example/entry.css */
div {
  background: url(./image-55DNWN2R.png);
}

    This is output from the previous version of esbuild. The above asset reference in out/example/entry.css is wrong. The path should start with ../ because the two files are in different directories.

    With this release, the asset references present in output files will now be the full relative path from the output file to the asset, so imports should now work correctly when the entry point is in a subdirectory within the output directory. This change affects asset reference paths in both CSS and JS output files.

    Note that if you want asset reference paths to be independent of the subdirectory in which they reside, you can use the --public-path setting to provide the common path that all asset reference paths should be constructed relative to. Specifically --public-path=. should bring back the old problematic behavior in case you need it.

  • Add support for [dir] in --asset-names (#​1196)

    You can now use path templates such as --asset-names=[dir]/[name]-[hash] to copy the input directory structure of your asset files (i.e. input files loaded with the file loader) to the output directory. Here's an example:

    $ cat entry.css
header {
  background: url(images/common/header.png);
}
main {
  background: url(images/home/hero.png);
}

$ esbuild --bundle entry.css --outdir=out --asset-names=[dir]/[name]-[hash] --loader:.png=file

$ find out -type f
out/images/home/hero-55DNWN2R.png
out/images/common/header-55DNWN2R.png
out/entry.css

$ cat out/entry.css
/* entry.css */
header {
  background: url(./images/common/header-55DNWN2R.png);
}
main {
  background: url(./images/home/hero-55DNWN2R.png);
}

v0.12.11

Compare Source

  • Enable faster synchronous transforms with the JS API by default (#​1000)

    Currently the synchronous JavaScript API calls transformSync and buildSync spawn a new child process on every call. This is due to limitations with node's child_process API. Doing this means transformSync and buildSync are much slower than transform and build, which share the same child process across calls.

    This release improves the performance of transformSync and buildSync by up to 20x. It enables a hack where node's worker_threads API and atomics are used to block the main thread while asynchronous communication with a single long-lived child process happens in a worker. Previously this was only enabled when the ESBUILD_WORKER_THREADS environment variable was set to 1. But this experiment has been available for a while (since version 0.9.6) without any reported issues. Now this hack will be enabled by default. It can be disabled by setting ESBUILD_WORKER_THREADS to 0 before running node.

  • Fix nested output directories with WebAssembly on Windows (#​1399)

    Many functions in Go's standard library have a bug where they do not work on Windows when using Go with WebAssembly. This is a long-standing bug and is a fault with the design of the standard library, so it's unlikely to be fixed. Basically Go's standard library is designed to bake "Windows or not" decision into the compiled executable, but WebAssembly is platform-independent which makes "Windows or not" is a run-time decision instead of a compile-time decision. Oops.

    I have been working around this by trying to avoid using path-related functions in the Go standard library and doing all path manipulation by myself instead. This involved completely replacing Go's path/filepath library. However, I missed the os.MkdirAll function which is also does path manipulation but is outside of the path/filepath package. This meant that nested output directories failed to be created on Windows, which caused a build error. This problem only affected the esbuild-wasm package.

    This release manually reimplements nested output directory creation to work around this bug in the Go standard library. So nested output directories should now work on Windows with the esbuild-wasm package.

v0.12.10

Compare Source

  • Add a target for ES2021

    It's now possible to use --target=es2021 to target the newly-released JavaScript version ES2021. The only difference between that and --target=es2020 is that logical assignment operators such as a ||= b are not converted to regular assignment operators such as a || (a = b).

  • Minify the syntax Infinity to 1 / 0 (#​1385)

    The --minify-syntax flag (automatically enabled by --minify) will now minify the expression Infinity to 1 / 0, which uses fewer bytes:

    // Original code
const a = Infinity;

// Output with "--minify-syntax"
const a = 1 / 0;

    This change was contributed by @​Gusted.

  • Minify syntax in the CSS transform property (#​1390)

    This release includes various size reductions for CSS transform matrix syntax when minification is enabled:

    /* Original code */
div {
  transform: translate3d(0, 0, 10px) scale3d(200%, 200%, 1) rotate3d(0, 0, 1, 45deg);
}

/* Output with "--minify-syntax" */
div {
  transform: translateZ(10px) scale(2) rotate(45deg);
}

    The translate3d to translateZ conversion was contributed by @​steambap.

  • Support for the case-sensitive flag in CSS attribute selectors (#​1397)

    You can now use the case-sensitive CSS attribute selector flag s such as in [type="a" s] { list-style: lower-alpha; }. Previously doing this caused a warning about unrecognized syntax.

v0.12.9

Compare Source

  • Allow this with --define (#​1361)

    You can now override the default value of top-level this with the --define feature. Top-level this defaults to being undefined in ECMAScript modules and exports in CommonJS modules. For example:

    // Original code
((obj) => {
  ...
})(this);

// Output with "--define:this=window"
((obj) => {
  ...
})(window);

    Note that overriding what top-level this is will likely break code that uses it correctly. So this new feature is only useful in certain cases.

  • Fix CSS minification issue with !important and duplicate declarations (#​1372)

    Previously CSS with duplicate declarations for the same property where the first one was marked with !important was sometimes minified incorrectly. For example:

    .selector {
  padding: 10px !important;
  padding: 0;
}

    This was incorrectly minified as .selector{padding:0}. The bug affected three properties: padding, margin, and border-radius. With this release, this code will now be minified as .selector{padding:10px!important;padding:0} instead which means there is no longer a difference between minified and non-minified code in this case.

sindresorhus/globby

v11.0.4

Compare Source

GoogleChrome/lighthouse

v7.5.0

Compare Source

Full Changelog

We expect this release to ship in the DevTools of Chrome 92, and to PageSpeed Insights within 2 weeks.

New contributors

Thanks to our new contributor 👽🐷🐰🐯🐻!

Notable Changes

We are releasing the Lighthouse Treemap!

You may already be familiar with treemaps thanks to webtreemap (which we use!) or source-map-explorer. With Lighthouse Treemap, you'll be able to view all the JavaScript bundles on your page easily from a Lighthouse report, in addition to some insights that may help reduce the amount of JavaScript on a page. The only requirement is that source maps are accessible (either publicly, or securely from the same computer that is running the Lighthouse audit).

We even collect code coverage data from Chrome, and extrapolate the coverage of individual modules in a bundle. Note: this only takes into account a cold-load: code only used after user interaction will be marked as unused. Stay tuned for a future release, which will enable you to configure user flows and capture even more accurate performance insights.

If we detect a large module included by multiple bundles, we'll alert you of that too.

You can access Lighthouse Treemap from the report:

Currently, only reports generated with the Lighthouse Node CLI will connect to the Lighthouse Treemap App. This functionality will be in DevTools and PageSpeed Insights as of Lighthouse v8.0.

Demo

Core

  • add new CLS (all frames) to hidden metrics audit (#​12476)
  • script-treemap-data: default config (#​12494)
  • script-treemap-data: include unmapped bytes (#​12452)
  • driver: extract gotoURL to navigation module (#​12421)
  • responsive-images: ignore images larger than viewport (#​12414)
  • robots: use new fetcher to get robots.txt (#​12423)

Fraggle Rock

Support for auditing user flows (#​11313)

  • computed-artifact: remove settings and options from context (#​12435)
  • convert optimized-images gatherer (#​12491)
  • convert image-elements gatherer (#​12474)
  • convert source-maps gatherer (#​12467)
  • convert js-usage gatherer (#​12450)
  • convert main-document-content gatherer (#​12470)
  • convert css-usage gatherer (#​12460)
  • convert trace-elements gatherer (#​12442)
  • extract warnings from gather-runner (#​12469)
  • extract driver preparation methods (#​12445)
  • extract navigation errors from gather-runner (#​12461)
  • split out DOM utilities from legacy driver (#​12431)
  • separate phase from gatherMode (#​12370)
  • add fetcher to transitional driver (#​12419)
  • add computed cache to pass context (#​12427)

Report

Deps

I18n

Docs

  • remove AMP Plugin example (#​12390)
  • add python requests install to webtests (#​12436)

Tests

  • update chromium installable source path (#​12364)
  • i18n: only accept IcuMessages in toBeDisplayString (#​12487)
  • add smokehouse to bin for downstream use (#​12446)
  • split CI into unit and smoke workflows (#​12422)
  • smoke: verify CSP violations caused by lighthouse (#​12391)
  • add organic TTI savings case to byte efficieny audit (#​12418)

Misc

  • treemap: esc to zoom out (#​12498)
  • treemap: remove too similar color hues (#​12497)
  • treemap: shade background for unused bytes (#​12486)
  • treemap: update colors on enter keypress (#​12496)
  • treemap: set focus-visible styles for view mode buttons (#​12495)
  • treemap: tweak styles for mobile (#​12493)
  • treemap: highlight treemap node on mouse hover table row (#​12483)
  • treemap: upgrade to 3.2.0 for keyboard navigation (#​12488)
  • treemap: use 0.1 for default granularity (#​12485)
  • treemap: remove byte size from title (#​12484)
  • treemap: add GA snippet for new property (#​12481)
  • treemap: i18n (#​12441)
  • treemap: fix colors (#​12462)
  • treemap: duplicate-modules view mode (#​12424)
  • treemap: add data table (#​12363)
  • cli: destructure args in import (#​12398)
  • move predictive-perf off renderer i18n (#​12482)
  • do not publish lighthouse-cli/test except smokehouse (#​12415)

v7.4.0

Compare Source

Full Changelog

We expect this release to ship in the DevTools of Chrome 92, and to PageSpeed Insights within 2 weeks.

New contributors

Thanks to our new contributors 👽🐷🐰🐯🐻!

Notable Changes

Core

  • csp-xss: hidden severity (#​12240)
  • deprecations: ignore warning for ::-webkit-details-marker (#​12341)
  • driver: move evaluateOnNewDocument to executionContext (#​12381)
  • fetcher: fetch over protocol (#​12199)
  • fetcher: disable auto-attaching for injected iframe (#​12347)
  • hreflang: use Audit.makeNodeItem (#​12273)
  • meta-elements: add NodeDetails (#​12274)
  • unsized-images: pass with explicit aspect-ratio (#​12377)

Fraggle Rock

Support for auditing user flows (#​11313)

  • extract storage and service worker driver methods (#​12400)
  • prepare emulation utilities for shared use (#​12375)
  • filter out manual-only categories (#​12367)
  • colocate PerformanceObserver installation with wait logic (#​12365)

CLI

  • asset-saver: print one devtoolsLog event per line (#​12348)

Report

Deps

I18n

Docs

  • architecture: augment gathering & artifacts descriptions (#​12368)
  • readme: add Alertdesk to the list of integrations (#​12356)

Tests

  • smoke request count assertion (#​12325)
  • remove flaky Chrome launch from unit-cli (#​12359)
  • retry some jest tests on failure (#​12298)
  • cron to check for relevant chromium changes (#​11763)
  • devtools: sync webtests (#​12310)
  • smoke: remove html imports from dbw_tester (#​12354)
  • smoke: update CLS-AF expectation (#​12353)
  • fix split of smoke tests across jobs (#​12323)
  • smoke: temporarily disable offline-warning check (#​12312)
  • smoke: remove max chrome for lantern script attribution (#​12270)

Misc

  • ci: increase yarn network timeout (#​12376)
  • treemap: root node selector (#​12360)
  • tweak unused-audits strings (remove -> reduce) (#​12281)
  • puppeteer script to test a page from devtools (#​12145)
  • treemap: tweak styles for logo spacing and text colors (#​12342)
  • fix path check for roll-devtools script (#​12358)
  • add patrickhulce back to issue assignment (#​12357)
  • fix open-devtools script (#​12313)
  • include SVG elements by default in typed querySelector (#​12307)
  • fix PhaseArtifact type to include Stacks (#​12280)
  • sentry: tag protocol method (#​12268)

v7.3.0

Compare Source

Full Changelog

We expect this release to ship in the DevTools of Chrome 91, and to PageSpeed Insights within 2 weeks.

New contributors

Thanks to our new contributor 👽🐷🐰🐯🐻!

New Audits

  • new_audit: csp-xss (experimental config) (#​12044)

Core

  • csp-xss: csp evaluator npm module (#​12221)
  • driver: remove unused goOffline/goOnline methods (#​12135)
  • errors-in-console: properly define default options (#​12200)
  • fr: convert base artifacts to gatherer artifacts (#​12129)

CLI

  • correctly parse screenEmulation boolean flags (#​12250)
  • only launch Chrome when running against localhost (#​12140)

Report

  • use css var for element screenshots, move overlay to container (#​12201)

Deps

  • update jsonld to latest (#​12257)
  • update typescript and axe-core to latest (#​12207)

I18n

Docs

  • fixed typo in documentation throttling.md (#​12154)

Tests

  • devtools: dynamically fetch chromium version (#​12232)
  • devtools: fix webserver (#​12236)
  • devtools: update chromium dependencies (#​12130)
  • fr: update test artifact (#​12202)
  • legacy-javascript: pin to specific versions of core-js (#​12265)
  • smoke: ignore lantern script attribution in ToT (#​12256)

Misc

  • treemap: unused-bytes view mode (#​12142)
  • remove patrickhulce from issue assigner (#​12220)
  • reorganize accessibility gatherer (#​12076)
mochajs/mocha

v8.4.0

Compare Source

🎉 Enhancements

🐛 Fixes

📖 Documentation

Also thanks to @​outsideris for various improvements on our GH actions workflows.

v8.3.2

Compare Source

🐛 Fixes

📖 Documentation

v8.3.1

Compare Source

🐛 Fixes

  • #​4577: Browser: fix EvalError caused by regenerator-runtime ([

Configuration

📅 Schedule: "before 3am on Monday" (UTC).

🚦 Automerge: Enabled.

♻ 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.

  • If you want to rebase/retry this PR, check this box.

This PR has been generated by WhiteSource Renovate. View repository job log here.

@samouri samouri merged commit 5e58687 into main Aug 2, 2021
@samouri samouri deleted the renovate/all branch August 2, 2021 14:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@samouri samouri samouri approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@samouri