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:
8.14.0
->8.19.0
8.14.0
->8.19.0
8.14.0
->8.19.0
8.14.0
->8.19.0
3.7.1
->3.7.2
9.21.0
->9.26.0
15.4.3
->15.5.2
8.14.0
->8.19.0
^0.16.0
->^0.18.0
3.5.2
->3.5.3
2.2.4
->2.2.6
Release Notes
salesforce/lwc (@lwc/compiler)
v8.19.0
Compare Source
Better types for template elements
TypeScript component authors can now specify a new property,
__lwc_public_property_types__
, to indicate to TypeScript which properties are available on the element created by a component. This prevents erroneous property definitions, which are otherwise unavoidable due to the way that TypeScript implements decorators.Example
In this example, the element interface for
c-inferred-props
is defined byLightningHTMLElement<InferredProps>
. That interface has an erroneous property definition,internal
. Theinternal
property is part of the component interface, but is not decorated with@api
, so it should not be part of the element interface.The element interface for
c-explicit-props
is defined byLightningHTMLElement<ExplicitProps>
. BecauseExplicitProps
defines__lwc_public_property_types__
, the element interface does not include theinternal
property, which is the correct behavior.What else changed?
Full Changelog: salesforce/lwc@v8.18.2...v8.19.0
v8.18.2
Compare Source
What's Changed
v3.0.0
by @divmain in https://github.com/salesforce/lwc/pull/5343lwc:on
directive by @divmain in https://github.com/salesforce/lwc/pull/5344Full Changelog: salesforce/lwc@v8.18.0...v8.18.2
v8.18.1
Compare Source
What's Changed
v8.18.0
Compare Source
What's Changed
Full Changelog: salesforce/lwc@v8.16.4...v8.18.0
v8.17.0
Compare Source
What's Changed
Full Changelog: salesforce/lwc@v8.16.4...v8.17.0
v8.16.5
Compare Source
What's Changed
v8.16.4
Compare Source
What's Changed
v8.16.3
Compare Source
What's Changed
v8.16.2
Compare Source
What's Changed
lwc-style
register util by @wjhsf in https://github.com/salesforce/lwc/pull/5277__lwc
for transmogrified function names by @wjhsf in https://github.com/salesforce/lwc/pull/5278v8.16.1
Compare Source
What's Changed
Full Changelog: salesforce/lwc@v8.16.0...v8.16.1
v8.16.0
Compare Source
What's Changed
Full Changelog: salesforce/lwc@v8.15.1...v8.16.0
v8.15.1
Compare Source
What's Changed
Full Changelog: salesforce/lwc@v8.15.0...v8.15.1
v8.15.0
Compare Source
What's Changed
generateMarkup
type defs by @wjhsf in https://github.com/salesforce/lwc/pull/5242New Contributors
Full Changelog: salesforce/lwc@v8.14.0...v8.15.0
salesforce/eslint-config-lwc (@salesforce/eslint-config-lwc)
v3.7.2
Compare Source
What's Changed
CONTRIBUTING.md
by @jmsjtu in https://github.com/salesforce/eslint-config-lwc/pull/153Full Changelog: salesforce/eslint-config-lwc@v3.7.1...v3.7.2
eslint/eslint (eslint)
v9.26.0
Compare Source
v9.25.1
Compare Source
v9.25.0
Compare Source
v9.24.0
Compare Source
v9.23.0
Compare Source
v9.22.0
Compare Source
lint-staged/lint-staged (lint-staged)
v15.5.2
Compare Source
Patch Changes
5561321
Thanks @YimingIsCOLD! - Correctly handle colon (:
) characters in staged filenames.v15.5.1
Compare Source
Patch Changes
#1533
5d53534
Thanks @iiroj! - Improve listing of staged files so that lint-staged doesn't crash when encountering an uninitialized submodule. This should result in less errors like:v15.5.0
Compare Source
Minor Changes
630af5f
Thanks @iiroj! - Lint-staged no longer resets to the original state when preventing an empty git commit. This happens when your configured tasks reset all the staged changes, typically when trying to commit formatting changes which conflict with your linter setup like ESLint or Prettier.Example with Prettier
By default Prettier prefers double quotes.
Previously
file.js
with only double quotes"
changed to'
git commit -am "I don't like double quotes"
prettier --write file.js
, converting all the'
back to"
'
are stagedNow
file.js
with only double-quotes"
changed to'
git commit -am "I don't like double quotes"
prettier --write file.js
, converting all the'
back to"
salesforce-experience-platform-emu/lwr (lwr)
v0.18.2
Compare Source
v0.18.1
Compare Source
v0.18.0
Compare Source
v0.17.7
Compare Source
v0.17.6
Compare Source
v0.17.5
Compare Source
v0.17.4
Compare Source
v0.17.3
Compare Source
v0.17.2
Compare Source
v0.16.13
Compare Source
v0.16.12
Compare Source
prettier/prettier (prettier)
v3.5.3
Compare Source
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, 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 was generated by Mend Renovate. View the repository job log.