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.
react-runner
Advanced tools
Run your React code on the go https://react-runner.vercel.app
render
or export default
Typescript
import
statement via createRequire
utilityHacker News in react-runner vs in real world, with the same code
# Yarn
yarn add react-runner
# NPM
npm install --save react-runner
string
, required the code to be ranobject
globals that could be used in code
{
React,
jsxPragma: React.createElement, // useful if you are using Emotion with `css` prop
jsxFragmentPragma: React.Fragment,
}
import { useRunner } from 'react-runner'
const { element, error } = useRunner({ code, scope })
or use Runner
as a component directly and handle error with onRendered
import { Runner } from 'react-runner'
const element = <Runner code={code} scope={scope} onRendered={handleRendered} />
import
statement// you can define your own version of `createRequire`
import { createRequire } from 'react-runner'
import * as YourPkg from 'your-pkg'
const scope = {
require: createRquire({
'your-pkg': YourPkg,
}),
}
then in your code you can use import Foo, { Bar } from 'your-pkg'
"browserslist": [
"Chrome > 61",
"Edge > 16",
"Firefox > 60",
"Safari > 10.1"
]
react-runner
is inspired by react-live heavily,
I love it, but I love arrow functions for event handlers instead of bind them manually as well as other modern features,
and I don't want to change my code to be compliant with restrictions, so I created this project,
use Sucrase instead of Bublé to transpile the code.
If you are using react-live
in your project and want a smooth transition, react-live-runner
is there for you which provide the identical way to play with, and react-live-runner
re-exports react-runner
so you can use everything in react-runner
by importing react-live-runner
import {
LiveProvider,
LiveEditor,
LiveError,
LivePreview,
} from 'react-live-runner'
...
<LiveProvider code={code} scope={scope}>
<LiveEditor />
<LivePreview />
<LiveError />
</LiveProvider>
...
or hooks for better custom rendering
import { useLiveRunner, CodeEditor } from 'react-live-runner'
const { element, error, code, onChange } = useLiveRunner({
initialCode,
scope,
transformCode,
})
...
<>
<CodeEditor value={code} onChange={onChange}>
<div>{element}</div>
{error && <pre>{error}</pre>}
</>
...
or use react-runner
directly
import { useState, useEffect } from 'react'
import { useRunner } from 'react-runner'
const [code, onChange] = useState(initialCode)
const { element, error } = useRunner({ code, scope })
useEffect(() => {
onChange(initialCode)
}, [initialCode])
...
<>
<textarea value={code} onChange={event => onChange(event.target.value)}>
<div>{element}</div>
{error && <pre>{error}</pre>}
</>
...
See the real world usage here https://github.com/nihgwu/react-runner/blob/master/website/src/components/LiveRunner.tsx
MIT © Neo Nie
FAQs
Run your React code on the go
The npm package react-runner receives a total of 12,904 weekly downloads. As such, react-runner popularity was classified as popular.
We found that react-runner demonstrated a healthy version release cadence and project activity because the last version was released less than 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.