
Security News
PyPI Expands Trusted Publishing to GitLab Self-Managed as Adoption Passes 25 Percent
PyPI adds Trusted Publishing support for GitLab Self-Managed as adoption reaches 25% of uploads
@injex/react-plugin
Advanced tools
The React plugin makes it easier to inject dependencies from an Injex container into React components using react hooks.
The Plugin creates a Context provider and exposes the useInjex() hook, so you can use Injex container API to inject your application modules into your application components.
You can install the React Plugin via NPM
npm install --save @injex/react-plugin
or Yarn
yarn add @injex/react-plugin
You should also make sure React and ReactDOM is installed on your project.
Creating the plugin and passing it to the runtime container config object
import { Injex } from "@injex/node";
import { ReactPlugin } from "@injex/react-plugin";
Injex.create({
rootDirs: [__dirname],
plugins: [
new ReactPlugin({
// plugin configurations
})
]
});
renderThe render function from React. The default is the render function from react-dom.
This configuration is pretty rare and it used where you have more than one react version in your application.
functionrender from react-domfalserootElementOrSelectorAn HTML element or string selector to use with the RenderInjexProvider method.
HTMLElement | stringnullfalseThe Injex React plugin is slightly different from the other plugins in a way you can use it without creating a plugin instance; here is a basic usage example.
import { Injex } from "@injex/webpack";
import { ReactPlugin } from "@injex/react-plugin";
Injex.create({
resolveContext: () => require.context(__dirname, true, /\.tsx?$/),
plugins: [
new ReactPlugin({
rootElementOrSelector: "#root"
})
]
}).bootstrap();
The rootElementOrSelector option tells the plugin where is the root container element for rendering the application, this is not a mandatory configuration and it's relevant only if you're going to use the renderInjexProvider method as described below.
renderInjexProvider methodThe most straightforward and easy way to use the plugin is by rendering your application using this injectable method. It will render your root component inside an Injex provider so you can use the useInjex() hook anywhere in your React application components.
import * as React from "react";
import { bootstrap, IBootstrap, inject } from "@injex/core";
import { RenderInjexProvider } from "@injex/react-plugin";
import App from "components/app";
@bootstrap()
export class Bootstrap implements IBootstrap {
@inject() private renderInjexProvider: RenderInjexProvider;
public run() {
this.renderInjexProvider(<App />);
}
}
The renderInjexProvider injectable method accepts two arguments. The first is the Root component we want to render into the container provided in the rootElementOrSelector plugin option. The second argument is optional, and it accepts the root element for rendering the component in case the rootElementOrSelector option was not provided; this will allow using the method multiple times with different root elements.
The method will render your root component inside an InjexProvider component to enable the use of the useInjex() hook.
InjexProviderSometimes you'll want to render the InjexProvider by yourself. Injex React plugin exposes the InjexProvider so you can use it while rendering your application. The provider accepts only one prop, the Injex runtime container itself, and you can access it using the @inject() decorator.
import * as React from "react";
import { render } from "react-dom";
import { bootstrap, IBootstrap, inject } from "@injex/core";
import { InjexProvider } from "@injex/react-plugin";
import App from "components/app";
@bootstrap()
export class Bootstrap implements IBootstrap {
@inject() private $injex;
public run() {
render(
<InjexProvider container={this.$injex}>
<App />
</InjexProvider>,
document.getElementById("root")
);
}
}
useInjex() hookThe useInjex() hook is the core of the Injex React plugin, making it possible to inject dependencies from your runtime container directly into your application components inside the InjexProvider.
Lets say you have a singleton session manager with a currentUser as a property:
import { define, singleton } from "@injex/core";
@define()
@singleton()
export class SessionManager {
public get currentUser() {
return {
name: "Udi Talias",
url: "https://twitter.com/uditalias"
};
}
}
You can inject it into your application components using the useInjex() hook:
import * as React from "react";
import { useInjex } from "@injex/react-plugin";
export default function App() {
const [inject, injectAlias] = useInjex();
// inject the singleton instance of the SessionManager
const session = inject("sessionManager");
return (
<h1>
Hello, <a href={session.currentUser.url}>{session.currentUser.name}</a>
</h1>
);
}
Note that useInjex() exposes two functions inside an array. The first is inject, which works the same as the @inject() decorator, and the second is the injectAlias that works the same as the @injectAlias() decorator.
If you want a quick demo to play with, check out the react example in the examples section.
FAQs
Unknown package
The npm package @injex/react-plugin receives a total of 9 weekly downloads. As such, @injex/react-plugin popularity was classified as not popular.
We found that @injex/react-plugin 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
PyPI adds Trusted Publishing support for GitLab Self-Managed as adoption reaches 25% of uploads

Research
/Security News
A malicious Chrome extension posing as an Ethereum wallet steals seed phrases by encoding them into Sui transactions, enabling full wallet takeover.

Security News
Socket is heading to London! Stop by our booth or schedule a meeting to see what we've been working on.