Skip to content

bug: connected/disconnectedCallback do not work in Mixins in React #769

@kyleMessnerLillyContractor

Description

Prerequisites

Framework Output Target

React (@stencil/react-output-target)

Output Target Version

1.4.2

Stencil Version

4.43.2

Reproduction URL

https://codesandbox.io/p/github/johnjenkins/stencil-starter-react/csb-lz2jvy/draft/objective-stonebraker

Describe the Bug

I am able to "properly" hook into lifecycle methods when the component is run as a web component but when the react-output-target version of the component runs the connectedCallback and disconnectedCallback methods stop working.

Not really sure if this is the right place for this issue so apologies if it should be reported in core

Steps to Reproduce

  • Use my-component outside of a react environment and observe equal logs from both the mixin and the component
  • Use my-component or MyComponent in a react project and observe that there are no connectedCallback or disconnectedCallback logs from the mixin

Expected Behavior

That Mixins in a React environment have the same way they behave in a native HTML environment

Additional Context

No response

Logs


Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions