%GetOptimizationStatus return a set of bitwise flags instead of a single value,
to access the value, you need to take the binary representation of the returned value.
Now, for example, if 65 is returned, the binary representation is the following:
(65).toString(2).padStart(12, '0');
// 000001000001Each binary digit acts as a boolean with the following meaning:
| function logger(strings,...values) { | |
| var str = ""; | |
| for (let i = 0; i < strings.length; i++) { | |
| if (i > 0) { | |
| if (values[i-1] && typeof values[i-1] == "object") { | |
| if (values[i-1] instanceof Error) { | |
| if (values[i-1].stack) { | |
| str += values[i-1].stack; | |
| continue; | |
| } |
| /** | |
| * @author ebidel@ (Eric Bidelman) | |
| * License Apache-2.0 | |
| */ | |
| // Prints the bytes cached by service worker. Breaks out each cache | |
| // overall in-memory bytes used by the Cache Storage API for the site. | |
| async function getCacheStoragesAssetTotalSize() { | |
| // Note: opaque (i.e. cross-domain, without CORS) responses in the cache will return a size of 0. |
The proposal you’re about to read is not just a proposal. We have a working implementation of almost everything we discussed here. We encourage you to checkout and build our branch: our fork, with the relevant branch selected. Building and using the implementation will give you a better understanding of what using it as a developer is like.
Our implementation ended up differing from the proposal on some minor points. As our last action item before making a PR, we’re writing documentation on what we did. While I loathe pointing to tests in lieu of documentation, they will be helpful until we complete writing docs: the unit tests.
This repo also contains a bundled version of npm that has a new command, asset. You can read the documentation for and goals of that comma
tl;dr I built a demo illustrating what it might look like to add async rendering to Facebook's commenting interface, while ensuring it appears on the screen simultaneous to the server-rendered story.
A key benefit of async rendering is that large updates don't block the main thread; instead, the work is spread out and performed during idle periods using cooperative scheduling.
But once you make something async, you introduce the possibility that things may appear on the screen at separate times. Especially when you're dealing with multiple UI frameworks, as is often the case at Facebook.
How do we solve this with React?
A tiny (265 byte) utility to create state machine components using two pure functions.
The API is a single function that accepts 2 pure functions as arguments:
| function ScriptAsyncAttrSupportPlugin() {} | |
| module.exports = ScriptAsyncAttrSupportPlugin; | |
| ScriptAsyncAttrSupportPlugin.prototype.apply = function(compiler) { | |
| compiler.plugin('this-compilation', function(compilation) { | |
| compilation.mainTemplate.plugin('bootstrap', function(source) { | |
| return this.asString([ | |
| source, | |
| '', |
| function ScriptAsyncAttrSupportPlugin() {} | |
| module.exports = ScriptAsyncAttrSupportPlugin; | |
| ScriptAsyncAttrSupportPlugin.prototype.apply = function(compiler) { | |
| compiler.plugin('this-compilation', function(compilation) { | |
| compilation.mainTemplate.plugin('bootstrap', function(source) { | |
| return this.asString([ | |
| source, | |
| '', |
| // Something like this. I haven't tested this file | |
| @Injectable() | |
| export class ApiService { | |
| constructor(public _http: Http, public _cache: Cache) { | |
| } | |
| // whatever domain/feature method name | |
| getModel(url) { | |
| // you want to return the cache if there is a response in it. This would cache the first response so if your API isn't idempotent you probably want to remove the item from the cache after you use it. LRU of 1 |
