react-i13n icon indicating copy to clipboard operation
react-i13n copied to clipboard

A performant, scalable and pluggable approach to instrumenting your React application.

Results 15 react-i13n issues
Sort by recently updated
recently updated
newest added

Use as a master tracker for 3.0.0 release. Enhancement: - [x] **[3.0.0-alpha.0]** Modernize package, publishing ES module and CJS - [x] Move to new React context API #190 - [x]...

# Description After setup an `i13nAnchor` component by using [email protected], get an unexpected root i13nNode in `created` event handler in existing plugins (ex. Rapid Plugin) ### 3.x version's payload.i13nNode is...

We could probably try to integrate intersection observer and fallback to the original logic if the browser doesnt support it. https://developer.mozilla.org/en-US/docs/Web/API/Intersection_Observer_API Also there is issue that currently the scroll event...

Certainly possible I'm misinterpreting the code, but it appears as if `_onEnterViewport ` is purposefully triggered if/when the tracked element does not exist. See https://github.com/yahoo/react-i13n/blob/master/src/libs/ViewportDetector.js#L56 In practice, I'm also noticing...

for example context.i13n.parentNode, shouldn't be accessed directly, add `_` to this.

we use pure js to render debug message tool because we are allow users to use mixin, and we cannot control render function, if we don't expose it and users...

https://github.com/yahoo/react-i13n/blob/master/src/utils/clickHandler.js#L15-L17 we use props to check new window, actually we should use a common way like `currentTarget` to do that

currently we only hook click event, support touch events like `tap`

Bumps [webpack-dev-server](https://github.com/webpack/webpack-dev-server) from 4.15.1 to 5.0.4. Release notes Sourced from webpack-dev-server's releases. v5.0.4 5.0.4 (2024-03-19) Bug Fixes security: bump webpack-dev-middleware (#5112) (aab576a) v5.0.3 5.0.3 (2024-03-12) Bug Fixes types: proxy (#5101)...

dependencies

👋 was poking around in this package's internals and noticed that components returned by `createI13nNode` seemingly accept an `i13n` prop in addition to `i13nModel`: https://github.com/yahoo/react-i13n/blob/aa16b9477220be5da01d42dcca17970a4b2e705d/src/core/createI13nNode.jsx#L41-L54 From what I can tell,...