Building a Live Editor
Published: ....
Last modified: ....
Share this post on BlueskySee discussion on Bluesky
As I have been working on my personal blog, I wanted to include the ability to edit code on site, and also preview it live. I started using react-live which I have had prior experience using and setting up, however I wanted to customize the theme of the editor a bit and try to work on a new and challenging task over the weekend.
So I decided to build @matthamlin/react-preview-editor
(see the project here).
Starting Off with Executing Code
I started off by looking at the source of react-live to figure out how they are
able to actually call the code that you edit inline. It turns out, that they use
the new Function
contructor to pass the code as a string along with an
assortment of the keys of the things within scope for the code, and then call
the function.
function evaluateCode(code, scope) {
// scope looks like this: { variableName: 'value' }
// construct a new function with the code
const func = new Function(...Object.keys(scope), code);
// Call the function
func(...Object.values(scope));
}
This allows us to evaluate code that the user types within the editor on the site, and probably goes without saying but could be a really bad™️ thing to do with live user input.
So now that we know how to actually execute the users code, how do we build the editor part?
The Code Editor
Well that part is actually pretty simple, because other awesome developers out there, have already shared open source projects for editing code within the browser. Since I wanted to keep the project fairly small, I went with react-simple-code-editor.
This editor allows me to control the highlighting of the code complete, and also is really easy to just start using:
<Editor
// Give it a value
value={code}
// Handle changes to the code
onValueChange={(code) => updateCode(code)}
// Provider it a function that returns a string or a React Node
// to highlight the code
highlight={highlighter}
/>;
Great, so we have a way to execute the code, and a way to edit the code, what about the syntax highlighting though?
Highlighting the Code
Well we are just as lucky as we were before, thanks to the
prism-react-renderer
library, we are able to use a React wrapping API around the prismjs
library.
This ends up looking like:
// This is the same function we pass to the Editor component above
function highlighter(code) {
return (
<Highlight {...defaultProps} code={code} language='jsx'>
{({ className, style, tokens, getLineProps, getTokenProps }) => (
<pre className={className} style={style}>
{tokens.map((line, i) => (
<div {...getLineProps({ line, key: i })}>
{line.map((token, key) => (
<span {...getTokenProps({ token, key })} />
))}
</div>
))}
</pre>
)}
</Highlight>
);
}
Wrapping Up
So wrapping it all up, we end up with an API that looks like this:
import { transform } from '@babel/standalone';
import { Editor, Preview, Provider } from '@matthamlin/react-preview-editor';
function transformCode(code) {
return transform(code, {
presets: [['stage-0', { decoratorsLegacy: true }], 'react'],
}).code;
}
const code = `
function App() {
return (
<p>Code Here!</p>
)
};
render(<App />);
`;
export default function App() {
return (
<Provider code={code} transformCode={transformCode}>
<Preview />
<Editor />
</Provider>
);
}
Be sure to checkout the project here: github.com/hamlim/react-preview-editor on GitHub (make sure to ⭐ it too 😆).
And check it out in CodeSandbox here.
Tags:
Related Posts
Development
Published: ....
I recently launched a rewrite and redesign of this personal website, I figured I'd talk a bit about the changes and new features that I added along the way!
Published: ....
A quick tip outlining how to provide specific TypeScript type definitions for a local module!
Published: ....
Slicing software: why vertical is better than horizontal.
Published: ....
What if you could author an entire web application in a single file?
Published: ....
Is it a good or a bad thing to offload writing code to AI agents and Large Language Models?
Published: ....
A brief look at Import Maps and package.json#imports to support isomorphic JavaScript applications!
Published: ....
A collection of tech talks that I regularly re-watch and also recommend to everyone!
Published: ....
Some features and functionality that I'd like within a React Server Component compatible framework.
Published: ....
A (running) collection of Bluesky tips, tools, packages, and other misc things!
Published: ....
How to generate a custom Ghostty theme based on any iterm2 theme!
Published: ....
A rough mental model for how you should be leveraging AI as a tool for your own growth
Published: ....
Even more thoughts on dogfooding!
Published: ....
The secret to excellent product teams is using your own product, and often!
Published: ....
(Ab)using Git as yet another tool for thought!
Published: ....
A quick look at the applications and tools that I (generally) use day to day for web development!
Published: ....
There are a variety of different markdown "standards" out there, and sometimes they're not all that consistent
Published: ....
There's a common gotcha when creating Web Request and Response instances with Headers!
Published: ....
Feature toggles are often underused by most software development teams, and yet offer so much value during not only feature development but also refactors
Published: ....
A quick introduction to my new side project, hohoro. An incremental JS/TS library build tool!
Published: ....
webpack, and tools built on it like Next.js, don't support true dynamic imports, but I found a way to trick the system!
Published: ....
I've been using a variety of AI tools as of late, I figured I'd document the ones I'm primarily using!
Published: ....
I've started to use Cloudflare to manage my domains for several side projects, have had to jump through the same hooks multiple times that I figured I should document them here!
Published: ....
Revising my previous blog post on React Error Boundaries and my preferred go-to implementation!
Published: ....
Two neat tricks for enhancing your site's favicon!
Published: ....
The various risks and pitfalls of open source software run by corporations.
Published: ....
A monorepo template for managing a library and documentation together.
Published: ....
How we solved an almost show-stopping production bug, and how you can avoid it in your own projects.
Published: ....
When did semver major changes become so scary?
Published: ....
No I don't mean those Milano cookies you keep taking from the office snack wall either (although you should probably stop snacking on those as often as well).
Published: ....
Pair programming can be good sometimes - but not all the time
Published: ....
A few quick thoughts on burn out and taking a break