componentpath-react-mixin
Advanced tools
React mixin to add data attribute to component element containing path to source file.
React mixin to add data attribute to component element containing path to source file. Very useful for QA and debugging code at runtime, particularly UI issues.
npm install componentpath-react-mixin
Require the mixin into your component and pass in the file path using the node '__dirname' variable:
var ComponentPathMixin = require('componentpath-react-mixin')(__dirname);
Then include the mixin as normal:
mixins: [ComponentPathMixin]
You can also pass context into your component path to differentiate between different insatnces of the same component. Just pass a 'componentContext' property into your component:
<ReactElement componentContext="context" />
0.0.1 Initial release 0.0.2 Created tests 0.0.3 Completed readme 1.0.0 Released to NPM 1.0.1 Added NPM badge to readme
FAQs
React mixin to add data attribute to component element containing path to source file.
The npm package componentpath-react-mixin receives a total of 2 weekly downloads. As such, componentpath-react-mixin popularity was classified as not popular.
We found that componentpath-react-mixin demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
React's CRA deprecation announcement sparked community criticism over framework recommendations, leading to quick updates acknowledging build tools like Vite as valid alternatives.
Security News
Ransomware payment rates hit an all-time low in 2024 as law enforcement crackdowns, stronger defenses, and shifting policies make attacks riskier and less profitable.
Security News
require(esm) backported to Node.js 20, easing the transition to ESM-only packages and reducing complexity for developers as Node 18 nears end-of-life.