Available on NPM as postscribe-umd. Will merge in all fixes that happen at krux/postscribe and some more.
Remote scripts, especially ads, block the page from doing anything else while they load. They contribute a large % to load times which affects your bottom line. Asynchronous ads do not block the page and can be delivered after core content - Async FTW.
Why is it so hard to deliver ads asynchronously? Because they may contain calls to document.write, which expects to be handled synchronously. PostScribe lets you deliver a synchronous ad asynchronously without modifying the ad code.
Shameless Plug: Using this standalone library is a great start, but if you want to go further and have your tags centrally managed instead of having them hard-coded on the page, Check out Krux's SuperTag, developed by the same authors as this library.
Other tag writing libraries exist (see alternatives), but PostScribe is novel in it's use of what we call DOM Proxies, a way to ensure that the content is written as close to the way the browser would natively write the content with document.write/innerHTML. Read: it behaves just like the browser would, without convoluted parsing or hacks.
For more information:
- Presentation at HTML5devconf by the author, Derek Brans
- Interactive Demo with side by side comparisons of other tag writers
- Documentation
- Browse the raw or annotated source code.
PostScribe overrides document.write. It is best and safest to use PostScribe after DOM is ready.
In a browser:
<script src="./dist/postscribe.min.js"></script>
With an AMD loader:
require(['postscribe'], function(postscribe) {});
In Node.js/io.js using CommonJS, first npm install --save postscribe, then:
var postscribe = require('postscribe');
To append html to #mydiv:
postscribe('#mydiv', '<h1>Hello PostScribe</h1>');
In general:
postscribe(element, html, options);
- element: a DOM Element, jQuery object, or id selector (e.g. "#mydiv")
- html: an html string or a function that takes a DOM Document and writes to it.
- options: a hash of options
- done: a callback that will be called when writing is finished.
If you just want to mess around, include the js files at the top of an html page that contains the following:
<div id="mydiv"></div>
<script type="text/javascript">
postscribe('#mydiv', '<h1>Hello PostScribe</h1>');
</script>
Where normally you would have
<div id="ad"><h5>Advertisement</h5>
<script type="text/javascript">
// Build url params and make the ad call
document.write('<script src=doubleclick_url_with_params><\/script>');
</script>
</div>
Instead, remove the ad call and close the div
<div id="ad"><h5>Advertisement</h5></div>
<script type="text/javascript">
// jQuery used as an example of delaying until load.
$(function() {
// Build url params and make the ad call
postscribe('#ad', '<script src=doubleclick_url_with_params><\/script>');
});
</script>
There are some hooks you may pass as the third argument. For example:
<script type="text/javascript">
// jQuery used as an example of delaying until load.
$(function() {
postscribe('#ad', '<script src=doubleclick_url_with_params><\/script>', {
done: function() {
console.info('Dblclick script has been delivered.');
}
});
});
</script>
See the beginning of postscribe.js for a complete list.
Yep. It neither depends on nor conflicts with any of the existing popular javascript frameworks.
Wat? No. Only one tag writer at a time.
This project was originally developed at Krux as part of its SuperTag product. There it was battle tested on high-profile sites like The New York Times, The Wall Street Journal, NBCU, and hundreds of others. It is actively maintained by Krux.
Postscribe was designed to behave as closely to the native document.write/innerHTML does as possible, and we've taken great care to make sure that it works on every browser we can get our hands on. We expect it to work on every browser built after 2005. There are over 400 unit tests that run on every commit, and we add more all the time. Postscribe is thoroughly tested and known to work well in the following browsers:
- Firefox - 3.6 and 4+
- Chrome 10+
- Safari - 5.0+
- Opera - 10.0+
- Internet Explorer 7+ (as far as we know, it will work on IE 6, but we're trying to encourage its death, so we haven't tested it)
- iPhone/iPad and other webkit-based browsers
Curious if a specific browser will work? Run the tests yourself and let us know if you see any failures.
We've stood on the shoulders of giants with our work, and there are other alternative approaches to solve this problem. Shout out to the best ones we found:
- writeCapture
- Ghostwriter by Digital Fulcrum (it looks like they have removed references to it on their site?)
- ControlJS by Steve Souders
If you would like your project to be added to this list, file an issue and we'd be happy to.
Have a problem? Need help? Would you like additional functionality added? We use github's ticket system for keeping track of these requests. Please check out the existing issues, and if you don't see that your problem is already being worked on, please file a new issue. The more information the better to describe your problem. We ♥ Jing bug reports.
We ♥ forks and pull requests.
To run the tests and static code analysis tools, you will need to have the following installed:
- nodejs (>=0.10) & npm - Install Instructions
- All other project dependencies are installed via npm with
npm install
Spaces, not tabs. 2 of them. jQuery's style guide covers just about everything else. Please do not update 3rd-party libraries (qunit, jquery) or the dist directory. We have an internal process for doing this.
Please include a jsfiddle or plunker that distills and reproduces the issue. Try forking this jsfiddle. We've set everything up there for you so that you can reproduce your issue.
Using travis-ci and grunt, the Qunit unit tests are run on every commit using PhantomJS to run the tests with a real browser.
Current Build Status:
To run the tests:
$ npm test
We use ESLint to do static analysis of the javascript and keep things smelling good. To run ESLint:
$ npm run lint
Pro Tip: You can use TDD and have ESLint and the tests run on every commit with:
$ npm run tdd
Postscribe uses software versioning standards as follows: major.new.maintenance[.trivial]. There are git tags for each release if you would like to see older versions.
- Support loading Postscribe as UMD module (browser global/CommonJS/AMD)
- Started building with Webpack. Running directly from source is no longer possible.
- Fix incomplete tags blocking UI thread
- beforeWriteToken hook
- Handle boolean attrs
- Comments fix
- Make autoFix a postscribe option
- Screwed up the tagging. (automation coming soon...)
- Adds hooks around queuing and stream starting.
- Adds option to not overwrite doc.write while script[async] is loading.
- iframe and textarea fix
- Error handling mod
- major refactoring to simplify code and fix rare bugs related to script tag handling
- scripts are now written inline
- htmlParser performance fix
- Test framework improvements
- Bug fixes
- Documentation release
- Documentation release
- Write tags asynchronously, yo. Initial release after 2+ years of development internally at Krux
We aim for you to use this inside your application, so we picked the least restrictive license we could find. MIT License - see LICENSE