chore(deps): bump eslint-plugin-jest from 24.3.6 to 25.2.4 #10080
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps [eslint-plugin-jest](https://github.com/jest-community/eslint-plugin-jest) from 24.3.6 to 25.2.4. - [Release notes](https://github.com/jest-community/eslint-plugin-jest/releases) - [Changelog](https://github.com/jest-community/eslint-plugin-jest/blob/main/CHANGELOG.md) - [Commits](jest-community/eslint-plugin-jest@v24.3.6...v25.2.4) --- updated-dependencies: - dependency-name: eslint-plugin-jest dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
added
dependencies
|
❌ Deploy Preview for carbon-react-next failed. 🔨 Explore the source changes: 28ec4e3 🔍 Inspect the deploy log: https://app.netlify.com/sites/carbon-react-next/deploys/618bb5fd3cadb50007f0c7f2 |
|
❌ Deploy Preview for carbon-elements failed. 🔨 Explore the source changes: 28ec4e3 🔍 Inspect the deploy log: https://app.netlify.com/sites/carbon-elements/deploys/618bb5fdab6b52000827fb6c |
|
❌ Deploy Preview for carbon-components-react failed. 🔨 Explore the source changes: 28ec4e3 🔍 Inspect the deploy log: https://app.netlify.com/sites/carbon-components-react/deploys/618bb5fdd5c1b40007928764 |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
dependabot
bot
deleted the
dependabot/npm_and_yarn/eslint-plugin-jest-25.2.4
branch
…ign-system#10080) ### Related Ticket(s) Closes carbon-design-system#9940 ### Description This PR takes a new approach, and offers some advantages of carbon-design-system#9941. While the other PR aims to separate class definitions from their registration in the browser, and should work well for teams or projects that wish to _extend_ C4IBM components, it does nothing to solve the problem for teams that are _double-consuming_ C4IBM components. For example, consider the widget team: - They are building widgets using the react-wrapper version of the components - When the react component imports the element, it brings along its `customElements.define()` method - The widget is placed on a page that is already using the C4IBM CDN links, which _also_ bring along the `customElements.define()` method. - Both the widget script and the CDN link are rolled up into separate scripts and whichever one runs second will encounter the unexpected error, not know how to handle that problem, and halt execution of the script, likely leaving large pieces of setup functionality unprocessed This new approach offers a method for elements to _attempt_ to define themselves, but to gracefully handle the failure and to continue executing the remainder of the running script. The new decorator is a simple copy/paste from the LitElement `@customElement` decorator, with the `customElements.define` functions wrapped in a try/catch block. As of right now, this only impacts one component and is simply a proof-of-concept. ### Changelog **New** - Adds a `@carbonElement()` decorator to the carbon-web-components package **Changed** - Edit the carbon-web-components package's accordion-item component to use @CarbonElement
Bumps eslint-plugin-jest from 24.3.6 to 25.2.4.
Release notes
Sourced from eslint-plugin-jest's releases.
... (truncated)
Changelog
Sourced from eslint-plugin-jest's changelog.
... (truncated)
Commits
7833de4chore(release): 25.2.4 [skip ci]a1296bdfix(prefer-to-be): preserveresolvesandrejectsmodifiers (#980)43e1722chore(deps): update yarn to v3.1.0 (#975)84bc605chore(deps): lock file maintenance1cfded5chore(release): 25.2.3 [skip ci]f468752fix(no-deprecated-functions): mark jest as an optional peer dependency (#970)5403268chore(deps): lock file maintenance59d86f5chore(deps): lock file maintenance4762ccedocs(prefer-lowercase-title): fix rule name in examples (#968)e7a9a9bchore(deps): update dependency@types/nodeto v16 (#967)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)