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 URLs 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 its URL and the proper URL extension.
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.
<pre id="output"></pre>
//makes all objects iterable just like Maps!!! YAY
//iterates over Object.keys() (which already ignores prototype chain for us)
Object.prototype[Symbol.iterator] = function() {
var keys = Object.keys(this)[Symbol.iterator]();
var obj = this;
var output;
return {next:function() {
if (!(output = keys.next()).done)
output.value = [output.value, obj[output.value]];
return output;
}};
};
Object.prototype.something = 'bob';
var ordinaryObject = {well:'hello', there:'!'};
//true Maps are just cumbersome to create
var trueMap = new Map([['well', 'hello'], ['there', '!']]);
//now that object is iterable we can create a real Map from it
var realMap = new Map(ordinaryObject);
var buf = '';
function output(string, indent) {
if (indent)
buf += '\t';
buf += string;
buf += '\n';
}
//problematic because it enumerates over prototypes
output('for in ordinary');
for (var name in ordinaryObject)
output(name + ':' + ordinaryObject[name], true);
output('');
output('for of Map');
for (let pair of trueMap)
output(pair[0] + ':' + pair[1], true);
output('fancier');
for (let [key, value] of trueMap)
output(key + ':' + value, true);
output('');
//MAGIC! yay!
output('for of ordinary with patch');
for (let pair of ordinaryObject)
output(pair[0] + ':' + pair[1], true);
output('fancier');
for (let [key, value] of ordinaryObject)
output(key + ':' + value, true);
output('');
//just to prove you can create real maps from it if you felt like it
output('for of Map constructed with ordinary notation');
for (let pair of realMap)
output(pair[0] + ':' + pair[1], true);
output('fancier');
for (let [key, value] of realMap)
output(key + ':' + value, true);
output('');
//apparently you can just do this, though
output('for of ordinary\'s keys');
for (let key of Object.keys(ordinaryObject))
output(key + ':' + ordinaryObject[key], true);
output('');
output('\n\n');
//note that maps force you to use .get() instead of [] notation
//outside of iterating, which is also annoying
output(trueMap.get('well'));
//but we get the best of both worlds with my way
//(well, asside from how inefficient the iterator creation is, but if you're really making maps to iterate A LOT you're probably doing something wrong)
output(ordinaryObject['well']);
document.getElementById('output').innerHTML = buf;
Also see: Tab Triggers