Skip to content

chore(npm) Update NPM #114

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.

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

chore(npm) Update NPM #114

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 3, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@lwc/compiler (source) 8.14.0 -> 8.19.0 age adoption passing confidence
@lwc/engine-dom (source) 8.14.0 -> 8.19.0 age adoption passing confidence
@lwc/engine-server (source) 8.14.0 -> 8.19.0 age adoption passing confidence
@lwc/synthetic-shadow (source) 8.14.0 -> 8.19.0 age adoption passing confidence
@salesforce/eslint-config-lwc 3.7.1 -> 3.7.2 age adoption passing confidence
eslint (source) 9.21.0 -> 9.26.0 age adoption passing confidence
lint-staged 15.4.3 -> 15.5.2 age adoption passing confidence
lwc (source) 8.14.0 -> 8.19.0 age adoption passing confidence
lwr (source) ^0.16.0 -> ^0.18.0 age adoption passing confidence
prettier (source) 3.5.2 -> 3.5.3 age adoption passing confidence
prettier-plugin-apex 2.2.4 -> 2.2.6 age adoption passing confidence

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

// <c-inferred-props>
class InferredProps extends LightningElement {
  @&#8203;api exposed = 'hello'
  internal = 'secret'
}

// <c-explicit-props>
class ExplicitProps extends InferredProps {
  __lwc_public_property_types__?: {
    exposed: string
  }
}

class Container extends LightningElement {
  checkInferred() {
    const inferred = this.querySelector<LightningHTMLElement<InferredProps>>('c-inferred-props')!
    inferred.exposed // ✅ Valid, no type error
    inferred.internal // ❌ Invalid, but no type error!
  }

  checkExplicit() {
    const explicit = this.querySelector<LightningHTMLElement<ExplicitProps>>('c-explicit-props')!
    explicit.exposed // ✅ Valid, no type error
    explicit.internal // ✅ Invalid, and a type error occurs!
  }
}

In this example, the element interface for c-inferred-props is defined by LightningHTMLElement<InferredProps>. That interface has an erroneous property definition, internal. The internal 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 by LightningHTMLElement<ExplicitProps>. Because ExplicitProps defines __lwc_public_property_types__, the element interface does not include the internal 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

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

v8.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
New 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

Full 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

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:

    ✖ Failed to get staged files!
    

v15.5.0

Compare Source

Minor Changes
  • #​1526 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
  1. Stage file.js with only double quotes " changed to '
  2. Run git commit -am "I don't like double quotes"
  3. Lint-staged runs prettier --write file.js, converting all the ' back to "
  4. Because there are now no changes, lint-staged fails, cancels the commit, and resets back to the original state
  5. Commit was not done, original state is restored and single quotes ' are staged
Now
  1. Stage file.js with only double-quotes " changed to '
  2. Run git commit -am "I don't like double quotes"
  3. Lint-staged runs prettier --write file.js, converting all the ' back to "
  4. Because there are now no changes, lint-staged fails and cancels the commit
  5. Commit was not done, and there are no staged changes
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.


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

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the chore label Mar 3, 2025
@renovate renovate bot changed the title chore(npm) Update dependency prettier to v3.5.3 chore(npm) Update NPM Mar 3, 2025
@renovate renovate bot force-pushed the renovate/npm branch 8 times, most recently from 5c4fde7 to 688974b Compare March 11, 2025 13:06
@renovate renovate bot force-pushed the renovate/npm branch 4 times, most recently from 15fb1c4 to 1ca9b26 Compare March 17, 2025 23:38
@renovate renovate bot force-pushed the renovate/npm branch 3 times, most recently from 10ab3b0 to ef7db0f Compare March 25, 2025 22:28
@renovate renovate bot force-pushed the renovate/npm branch 2 times, most recently from e6611f0 to 8a96dea Compare April 1, 2025 13:10
@renovate renovate bot force-pushed the renovate/npm branch 5 times, most recently from cb9a1fb to 80a2fce Compare April 11, 2025 19:57
@renovate renovate bot force-pushed the renovate/npm branch 3 times, most recently from 43c3f0c to dfd692e Compare April 18, 2025 18:48
@renovate renovate bot force-pushed the renovate/npm branch 2 times, most recently from 0b6d3f5 to 4468e2b Compare April 24, 2025 06:47
@renovate renovate bot force-pushed the renovate/npm branch 3 times, most recently from 3f326c5 to c92c6c9 Compare May 2, 2025 22:09
@renovate renovate bot force-pushed the renovate/npm branch from c92c6c9 to f2461ac Compare May 6, 2025 11:25
@renovate renovate bot force-pushed the renovate/npm branch from f2461ac to 363274b Compare May 9, 2025 23:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants