Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
lightweight-react-modal
Advanced tools
Lightweight react modal component.
npm i lightweight-react-modal
import React from 'react';
import {
Modal,
ModalHeader,
ModalContent,
ModalFooter,
} from 'lightweight-react-modal';
<Modal>
<ModalHeader>
Modal Header.
</ModalHeader>
<ModalContent>
Modal Content.
</ModalContent>
<ModalFooter>
Modal Footer.
</ModalFooter>
</Modal>
Name | Type | Description | Default value |
---|---|---|---|
onClose | func | On close callback. | null |
fluid | func | Sets the width and height to 90% of the screen. | false |
closable | bool | Makes modal closable/unclosable. | true |
maxHeight | number | Sets modal max height. | 500 |
minHeight | number | Sets modal min height. | 100 |
maxWidth | number | Sets modal max width. | 500 |
minWidth | number | Sets modal min width. | 200 |
customClassNames | shape({ wrapper: string, modal: string, closeBtn: string, overlay:string }) | Modal custom classNames. | null |
closeButtonIcon | node | Modifies close button icon. | null |
Name | Type | Description | Default value |
---|---|---|---|
className | string | Applies extra className. | null |
You can use ModalContext to get better control of modal in your application. With help of ModalContext you can trigger one or multiple modals from anywhere in our application.
import React from 'react';
import ReactDom from 'react-dom';
import {
Modal,
ModalContent,
ModalProvider,
} from 'lightweight-react-modal';
const ModalExample = ({ modal }) => (
<>
<button
type="button"
onClick={modal.toggle('modal_name')}
>
Toggle modal
</button>
{modal.isOpen('modal_name') ? (
<Modal>
<ModalContent>
Modal
</ModalContent>
</Modal>
) : null}
</>
);
const App = () => (
<ModalProvider>
<ModalHookExample />
</ModalProvider>
);
ReactDom.render(<App />, document.getElementById('app'));
import React from 'react';
import ReactDom from 'react-dom';
import {
Modal,
ModalContent,
ModalProvider,
useModalContext,
} from 'lightweight-react-modal';
const ModalHookExample = ({ modal }) => {
const modal = useModalContext();
return (
<>
<button
type="button"
onClick={modal.toggle('modal_name')}
>
Toggle modal
</button>
{modal.isOpen('modal_name') ? (
<Modal>
<ModalContent>
Modal
</ModalContent>
</Modal>
) : null}
</>
);
};
const App = () => (
<ModalProvider>
<ModalHookExample />
</ModalProvider>
);
ReactDom.render(<App />, document.getElementById('app'));
ModalProvider methods
Name | params | Description |
---|---|---|
open(name) | name: string/number | opens modal. |
close(name) | name: string/number | closes modal. |
toggle(name) | name: string/number | toggles modal. |
closeAll() | - | closes all opened modals. |
isOpen(name) | name: string/number | checks if modal is opened. |
isClose(name) | name: string/number | checks if modal is closed. |
list | - | returns list of opened modals. |
FAQs
lightweight react modal
The npm package lightweight-react-modal receives a total of 7 weekly downloads. As such, lightweight-react-modal popularity was classified as not popular.
We found that lightweight-react-modal 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
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.