chore(deps): update devdependencies #1091
Merged
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:
~0.14.45
->~0.14.46
~8.17.0
->~8.18.0
~39.3.2
->~39.3.3
Release Notes
evanw/esbuild
v0.14.46
Compare Source
Add the ability to override support for individual syntax features (#2060, #2290, #2308)
The
target
setting already lets you configure esbuild to restrict its output by only making use of syntax features that are known to be supported in the configured target environment. For example, settingtarget
tochrome50
causes esbuild to automatically transform optional chain expressions into the equivalent older JavaScript and prevents you from using BigInts, among many other things. However, sometimes you may want to customize this set of unsupported syntax features at the individual feature level.Some examples of why you might want to do this:
JavaScript runtimes often do a quick implementation of newer syntax features that is slower than the equivalent older JavaScript, and you can get a speedup by telling esbuild to pretend this syntax feature isn't supported. For example, V8 has a long-standing performance bug regarding object spread that can be avoided by manually copying properties instead of using object spread syntax. Right now esbuild hard-codes this optimization if you set
target
to a V8-based runtime.There are many less-used JavaScript runtimes in addition to the ones present in browsers, and these runtimes sometimes just decide not to implement parts of the specification, which might make sense for runtimes intended for embedded environments. For example, the developers behind Facebook's JavaScript runtime Hermes have decided to not implement classes despite it being a major JavaScript feature that was added seven years ago and that is used in virtually every large JavaScript project.
You may be processing esbuild's output with another tool, and you may want esbuild to transform certain features and the other tool to transform certain other features. For example, if you are using esbuild to transform files individually to ES5 but you are then feeding the output into Webpack for bundling, you may want to preserve
import()
expressions even though they are a syntax error in ES5.With this release, you can now use
--supported:feature=false
to forcefeature
to be unsupported. This will cause esbuild to either rewrite code that uses the feature into older code that doesn't use the feature (if esbuild is able to), or to emit a build error (if esbuild is unable to). For example, you can use--supported:arrow=false
to turn arrow functions into function expressions and--supported:bigint=false
to make it an error to use a BigInt literal. You can also use--supported:feature=true
to force it to be supported, which means esbuild will pass it through without transforming it. Keep in mind that this is an advanced feature. For most use cases you will probably want to just usetarget
instead of using this.The full set of currently-allowed features are as follows:
JavaScript:
arbitrary-module-namespace-names
array-spread
arrow
async-await
async-generator
bigint
class
class-field
class-private-accessor
class-private-brand-check
class-private-field
class-private-method
class-private-static-accessor
class-private-static-field
class-private-static-method
class-static-blocks
class-static-field
const-and-let
default-argument
destructuring
dynamic-import
exponent-operator
export-star-as
for-await
for-of
generator
hashbang
import-assertions
import-meta
logical-assignment
nested-rest-binding
new-target
node-colon-prefix-import
node-colon-prefix-require
nullish-coalescing
object-accessors
object-extensions
object-rest-spread
optional-catch-binding
optional-chain
regexp-dot-all-flag
regexp-lookbehind-assertions
regexp-match-indices
regexp-named-capture-groups
regexp-sticky-and-unicode-flags
regexp-unicode-property-escapes
rest-argument
template-literal
top-level-await
typeof-exotic-object-is-object
unicode-escapes
CSS:
hex-rgba
rebecca-purple
modern-rgb-hsl
inset-property
nesting
Since you can now specify
--supported:object-rest-spread=false
yourself to work around the V8 performance issue mentioned above, esbuild will no longer automatically transform all instances of object spread when targeting a V8-based JavaScript runtime going forward.Note that JavaScript feature transformation is very complex and allowing full customization of the set of supported syntax features could cause bugs in esbuild due to new interactions between multiple features that were never possible before. Consider this to be an experimental feature.
Implement
extends
constraints oninfer
type variables (#2330)TypeScript 4.7 introduced the ability to write an
extends
constraint after aninfer
type variable, which looks like this:You can read the blog post for more details: https://devblogs.microsoft.com/typescript/announcing-typescript-4-7/#extends-constraints-on-infer-type-variables. Previously this was a syntax error in esbuild but with this release, esbuild can now parse this syntax correctly.
Allow
define
to match optional chain expressions (#2324)Previously esbuild's
define
feature only matched member expressions that did not use optional chaining. With this release, esbuild will now also match those that use optional chaining:This is for compatibility with Webpack's
DefinePlugin
, which behaves the same way.eslint/eslint
v8.18.0
Compare Source
Features
a6273b8
feat: account for rule creation time in performance reports (#15982) (Nitin Kumar)Bug Fixes
f364d47
fix: Make no-unused-vars treat for..of loops same as for..in loops (#15868) (Alex Bass)Documentation
4871047
docs: Update analytics, canonical URL, ads (#15996) (Nicholas C. Zakas)cddad14
docs: Add correct/incorrect containers (#15998) (Nicholas C. Zakas)b04bc6f
docs: Add rules meta info to rule pages (#15902) (Nicholas C. Zakas)1324f10
docs: unify the wording referring to optional exception (#15893) (Abdelrahman Elkady)ad54d02
docs: add missing trailing slash to some internal links (#15991) (Milos Djermanovic)df7768e
docs: Switch to version-relative URLs (#15978) (Nicholas C. Zakas)21d6479
docs: change some absolute links to relative (#15970) (Milos Djermanovic)f31216a
docs: Update README team and sponsors (ESLint Jenkins)Build Related
ed49f15
build: remove unwanted parallel and image-min for dev server (#15986) (Strek)Chores
f6e2e63
chore: fix 'replaced by' rule list (#16007) (Milos Djermanovic)d94dc84
chore: remove unused deprecation warnings (#15994) (Francesco Trotta)cdcf11e
chore: fix versions link (#15995) (Milos Djermanovic)d2a8715
chore: add trailing slash topathPrefix
(#15993) (Milos Djermanovic)58a1bf0
chore: tweak URL rewriting for local previews (#15992) (Milos Djermanovic)80404d2
chore: remove docs deploy workflow (#15984) (Nicholas C. Zakas)71bc750
chore: Set permissions for GitHub actions (#15971) (Naveen)90ff647
chore: avoid generating subdirectories for each page on new docs site (#15967) (Milos Djermanovic)gajus/eslint-plugin-jsdoc
v39.3.3
Compare Source
Bug Fixes
check-line-alignment
: if no types are present, avoid allocating extra space; fixes #891 (26e7357)Configuration
📅 Schedule: Branch creation - "before 2am" (UTC), 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.