HTML preprocessors can make writing HTML more powerful or convenient. For instance, Markdown is designed to be easier to write and read for text documents and you could write a loop in Pug.
In CodePen, whatever you write in the HTML editor is what goes within the <body>
tags in a basic HTML5 template. So you don't have access to higher-up elements like the <html>
tag. If you want to add classes there that can affect the whole document, this is the place to do it.
In CodePen, whatever you write in the HTML editor is what goes within the <body>
tags in a basic HTML5 template. If you need things in the <head>
of the document, put that code here.
The resource you are linking to is using the 'http' protocol, which may not work when the browser is using https.
CSS preprocessors help make authoring CSS easier. All of them offer things like variables and mixins to provide convenient abstractions.
It's a common practice to apply CSS to a page that styles elements such that they are consistent across all browsers. We offer two of the most popular choices: normalize.css and a reset. Or, choose Neither and nothing will be applied.
To get the best cross-browser support, it is a common practice to apply vendor prefixes to CSS properties and values that require them to work. For instance -webkit-
or -moz-
.
We offer two popular choices: Autoprefixer (which processes your CSS server-side) and -prefix-free (which applies prefixes via a script, client-side).
Any URL's added here will be added as <link>
s in order, and before the CSS in the editor. You can use the CSS from another Pen by using it's URL and the proper URL extention.
You can apply CSS to your Pen from any stylesheet on the web. Just put a URL to it here and we'll apply it, in the order you have them, before the CSS in the Pen itself.
You can also link to another Pen here (use the .css
URL Extension) and we'll pull the CSS from that Pen and include it. If it's using a matching preprocessor, use the appropriate URL Extension and we'll combine the code before preprocessing, so you can use the linked Pen as a true dependency.
JavaScript preprocessors can help make authoring JavaScript easier and more convenient.
Babel includes JSX processing.
Any URL's added here will be added as <script>
s in order, and run before the JavaScript in the editor. You can use the URL of any other Pen and it will include the JavaScript from that Pen.
You can apply a script from anywhere on the web to your Pen. Just put a URL to it here and we'll add it, in the order you have them, before the JavaScript in the Pen itself.
If the script you link to has the file extension of a preprocessor, we'll attempt to process it before applying.
You can also link to another Pen here, and we'll pull the JavaScript from that Pen and include it. If it's using a matching preprocessor, we'll combine the code before preprocessing, so you can use the linked Pen as a true dependency.
Search for and use JavaScript packages from npm here. By selecting a package, an import
statement will be added to the top of the JavaScript editor for this package.
Using packages here is powered by Skypack, which makes packages from npm not only available on a CDN, but prepares them for native JavaScript ES6 import
usage.
All packages are different, so refer to their docs for how they work.
If you're using React / ReactDOM, make sure to turn on Babel for the JSX processing.
If active, Pens will autosave every 30 seconds after being saved once.
If enabled, the preview panel updates automatically as you code. If disabled, use the "Run" button to update.
If enabled, your code will be formatted when you actively save your Pen. Note: your code becomes un-folded during formatting.
Visit your global Editor Settings.
// used to retrieve template content
const templates = new WeakMap;
// used to retrieve node updates
const updates = new WeakMap;
// hyperHTML, the nitty gritty
function hyperHTML(chunks, ...interpolations) {
// if the static chunks are unknown
// (once per application)
if (!templates.has(chunks)) {
// use modern HTMLTemplateElement ...
const template = document.createElement('template');
// ... to reliably inject content joined by a unique comment
template.innerHTML = chunks.join('<!--⚡️-->');
// associate unique chunks to ...
templates.set(chunks, {
// ... the DocumentFragment within the template ...
content: template.content,
// ... and a list of paths to retrieve nodes to update
paths: [].filter.call(
template.content.childNodes,
// consider only comments with the unique content
node => node.nodeType === Node.COMMENT_NODE &&
node.textContent === '⚡️'
).map(node => {
// a comment is no layout, but it's handy to have it around
// what we want though, is a text node to show our content
node = node.parentNode.insertBefore(
node.ownerDocument.createTextNode(''),
node
);
// we can now create a path to find the node
// which is used once on first template setup
// [0, 1] for <p>Hello <!--⚡️--></p>
const path = [];
do {
path.unshift(path.indexOf.call(node.parentNode.childNodes, node));
node = node.parentNode;
} while(node !== template.content);
return path;
})
});
}
// if the current context has no updates available ...
// (once per node that uses this specific template)
if (!updates.has(this) || updates.get(this).chunks !== chunks) {
// ... grab related info
const info = templates.get(chunks);
// ... clean up the node
this.textContent = '';
// ... append a deep clone of the template content ...
this.appendChild(info.content.cloneNode(true));
// ... and save details for the next update
updates.set(this, {
// used to check the node is rendering the expected template
chunks,
// find all nodes that need to be updated
// save it as callback to invoke per each update
fns: info.paths.map(path => {
const node = path.reduce((p, i) => p.childNodes[i], this);
return text => node.textContent = text;
})
});
}
// we are now sure the template is known
// the content of the context is the epxected one
// and there is a list of updates to invoke
updates.get(this).fns.forEach((fn, i) => fn(interpolations[i]));
return this;
}
// example
// bind a node to hyperHTML
const render = hyperHTML.bind(document.body);
// update at speed light its content
(function showTime() {
requestAnimationFrame(showTime);
render`about the time ${
(new Date).toISOString().replace(/^.+T|Z$/g, '')
}`;
}());
Also see: Tab Triggers