Prism plugin for Torque: https://github.com/v8/v8.dev/blob/master/prism/torque.js

For assembly, Prism.languages.asm = Prism.languages.nasm; might be good enough (PrismJS/prism#482).

To enable these, we’re blocked on 11ty/eleventy-plugin-syntaxhighlight#4.

https://v8.dev/docs/source-code#viewing-the-try-server

https://v8.dev/docs/profile#profiling-web-applications

Similar to #243, https://github.com/v8/v8.dev/blob/master/src/_img/v8-lite/memory-categorization.svg embeds PNG image data. Unlike #243 however, in this case the entire image should be representable as properly scalable SVG (as it’s just a chart).

Screenshot from https://v8.dev/blog/v8-release-75#numeric-separators:

• Upstream issue: PrismJS/prism#1893
• Upstream patch by @RunDevelopment: PrismJS/prism#1895

/docs/torque would be nice.

https://v8.dev/docs/csa-builtins could be updated to cross-reference it, or even be replaced by it.

This is important since we currently recommend that all new built-ins are written in Torque.

cc @dannoc

• https://docs.google.com/document/d/1GU1ubYuNY5GSQvS874hB4xP2wopleo-X-DR4DUwFWAE/edit
• Torque user manual

Maybe /presentations?

Currently, we have:

• https://v8.dev/docs/node-integration
• https://v8.dev/docs/node-next-generation

This split was fine during the transition period, but nowadays the former is not useful anymore, and it’s superseded by the former. We should:

• move the contents of /docs/node-next-generation to /docs/node-integration
• set up a 301 redirect from /docs/node-next-generation to /docs/node-integration

@hashseed, do you want to take this on?

This is a follow-up to #240 which was closed by @dtig, but the issue isn’t resolved, so I don’t feel that it should be closed. This issue is, unfortunately, making it harder for me to do some work that I’m doing with V8.

As I mentioned in #240:

When I try v8.dev from my tablet without VPN, it works, but on my laptop with VPN, all of my requests are dropped. Barring disabling my VPN (which is a non-option for me on my laptop, unfortunately), there’s nothing that I can do on my end. Is there a policy against VPN users? If not, can y’all update the firewall settings?

Thank you.

We could host the HTML files + assets for Turbolizer, parse-processor, etc. under v8.dev/tools/* if we wanted to.

This seems like a good idea, but an open question remains how we'll keep it in sync with the V8 repo. Requiring a manual PRs for every change seems awkward. We could set up a bot to automate sending such PRs, but there'd still be some overhead.

Ideally, we'd be able to simply proxy through to the source files in the V8 repo. Perhaps using a rawgit-like Firebase function is the way to go here?

• https://developers.google.com/web/updates/2017/07/upcoming-regexp-features by @schuay and @hashseed
• https://developers.google.com/web/fundamentals/primers/async-functions by @jakearchibald
• https://developers.google.com/web/fundamentals/primers/promises by @jakearchibald

For a long time, https://v8.paulfryzel.com/docs/master was the place to go for up-to-date documentation on V8's public (and private) API surface. Unfortunately, this incredible resource is no longer maintained. v8.dev seems like an excellent place to host an official version of doxygen, although I don't know exactly how one would go about wiring that up. Perhaps a github action on https://github.com/v8/v8?

https://v8.dev/blog/real-world-performance mentions it and links to the slide deck. We should have a separate page on https://v8.dev/docs/rcs.

Are the following sections still accurate?

• https://v8.dev/docs/i18n#alternative-icu-checkout
• https://v8.dev/docs/i18n#system-icu

If yes, please close this issue. If not, please submit a patch.

Thanks!

https://v8.dev/blog/v8-release-69

Embedded built-ins go one step further.

…could be:

[Embedded built-ins](/blog/embedded-builtins) go one step further.

…and “Expect more details soon in a dedicated blog post” could be updated to say “For more details, see our dedicated blog post” or something similar.

Hello!

First of all, thank you for your work on this precious resource.

I have a proposal. It would be cool to see translation of articles in the blog into different languages. What do you think?

I think the community will help with translation (for example I can help with translation to Russian). In the code itself we need to add some changes to static site generator and add button for changing of language of the article.

We’re not using Google Tag Manager’s additional functionality so let’s use vanilla Google Analytics instead.

https://v8.dev/docs/d8-android#compile-spidermonkey-for-lollipop

Shouldn't the Liftoff logo with the outline have the dark gray thing above the blue circle, same as the original?

It's kinda hard to find the info I'm looking for if I don't know the exact page. Previously I used the github search to find stuff on the wiki.

We should be able to do better than html, img, h1 a, #footer { filter: invert(1); } 👻

Ugly screenshot of the above:

https://v8.dev/docs/become-committer#setting-up-push-access-to-the-repository

We can make the switch as soon as firebase/firebase-tools#876 is resolved.

Thank y'all for the v8 site - it's fantastic!

Example Page

https://v8.dev/docs/build

Screenshot

Problem

The code blocks stretch out a bit too far on the right. These declarations are responsible:

width: calc(100% + 4em);
width: calc(100% + var(--offset)*2);

Dropping the declaration(s) fixes the width.

After Screenshot

https://v8.dev/docs/blink-layout-tests

I'm having troubles with the third point (rebaselining the tests in Chromium), if you try to commit [ NeedsRebaseline ] it will fail during presubmit checks (as you can see here).

Another document exists with a manual way to do it (which is known to work): https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_tests.md#Rebaselining-Web-Tests.

Status: I'm currently following it and I can report the result here.

Per @tomayac's tweet, our current intrinsicsize should be changed to simple width/height attributes.

Introduction

iOS 12 Safari shows an error saying “response server by service worker has redirections” and refuses to open the page. This happens after the service worker has been installed i.e. after the first couple visits.

Error

How to Reproduce

1. Visit v8.dev and bookmark the site
2. Close the tab and then close the browser
3. Reopen safari and open the bookmark. If the error doesn’t appear, repeat this step.

Edit

I forgot to mention that I had ServiceWorkers enabled which is an experimental option in safari. So this is likely a safari bug. To turn on service workers: Settings>Safari>Advanced>Experimental Features>ServiceWorker>ON.

e.g. In the title for this page, & shows in the title bar.

on the other hand,when i run start and then input 'http://localhost:9001' in chrome,the response is

thanks:)

workbox-sw.js:1 Unable to import module 'workbox-google-analytics' from 'https://storage.googleapis.com/workbox-cdn/releases/3.6.1/workbox-google-analytics.prod.js'.
loadModule @ workbox-sw.js:1
get @ workbox-sw.js:1
(anonymous) @ sw.js:1
workbox-sw.js:1

Uncaught 
loadModule @ workbox-sw.js:1
get @ workbox-sw.js:1
(anonymous) @ sw.js:1

(index):1 Uncaught (in promise) TypeError: Failed to register a ServiceWorker: ServiceWorker script evaluation failed

Might be more of a workbox issue, but seems bad.

It might make sense to leave a comment linking to https://github.com/v8/v8/blob/master/src/torque/torque-parser.cc to the file as well.

E.g. https://raw.githubusercontent.com/v8/v8.dev/master/src/blog/array-sort.md has:

---
title: 'Getting things sorted in V8'
author: 'Simon Zünd ([@nimODota](https://twitter.com/nimODota)), consistent comparator'
avatars:
  - simon-zuend
date: 2018-09-28 11:20:37
tags:
  - ECMAScript
  - internals
description: 'Starting with V8 v7.0 / Chrome 70, Array.prototype.sort is stable.'
tweet: '1045656758700650502'
---

We should add a lint check that ensures this field is present for any new files that are added in PRs. The difficulty is that not all existing pages have this field.

e.g.:

https://v8.dev/docs/turbofan
https://v8.dev/docs/ignition
https://v8.dev/docs/untrusted-code-mitigations
...

https://v8.dev/docs/test

Does anyone still use make to build V8?

tools/run-tests.py --download-data is similarly outdated.

https://chromium-review.googlesource.com/c/v8/v8/+/1307423 removed tools/presubmit.py as instructed here https://v8.dev/docs/contribute#submit-your-code.

I'm not sure how to update it and if that's the correct place to complain about, but at least It will ping the website team. Thanks!

All images in src/_img/avatars/* follow certain conventions:

• JPEG format
• the @2x version is named [email protected] and must be exactly 192×192px
• the @1x version is named first-last.jpg and must be exactly 96×96px
• all images must be optimized i.e. below a certain file size threshold (10 kB?)
  • I tend to use Squoosh with MozJPEG @ quality=75, and then run the result through ImageOptim.app with “optimization level” set to “insane” for further savings.

All of the above could use automated CI checks, so that we don’t accidentally merge PRs that deviate from the convention.

https://v8.dev/docs/d8-android

https://chromium.googlesource.com/chromium/src/+/master/docs/testing/layout_tests.md and https://chromium.googlesource.com/chromium/src/+/master/docs/testing/layout_test_expectations.md#How-to-rebaseline are dead.

Our (youtube) video embeds don't preserve aspect ratio properly. This could be fixed with markdown-it-video and proper CSS (bmeurer/benediktmeurer.de@f6054bd gives an idea). The difference can be seen between https://v8.dev/blog/fast-async and https://benediktmeurer.de/2018/11/12/faster-async-functions-and-promises/ on a phone or in DevTools using the Toggle device toolbar feature.

I was just browsing the Torque user manual and thought a table of contents or something similar would be nice for larger articles. Especially for articles like the torque user manual, where readers might only be interested in one specific section.

https://v8.dev/docs/embed#advanced-guide (source: https://github.com/v8/v8.dev/blob/master/src/docs/embed.md) contains a link to https://v8.dev/docs/design-elements with the link text "V8 Design Elements". There is no page there (it's a 404).

The relevant wiki page says the page has moved to https://v8.dev/ but I couldn't find anything on v8.dev that looked like a "design elements" doc.

For the feature support listings on v8.dev/features, we started small and shipped a manually maintained version. The maintenance overhead is acceptable, since once a feature ships in any one environment, we can update our feature support listing, and then we (generally) never have to update that specific feature+environment entry again.

However, it would be nice to automate this whole thing, and use a centralized data source like ChromeStatus, CanIUse, or MDN.

Unfortunately, v8.dev has been down for at least a week now. Are y’all aware of this?

Thank you.

Example link: https://v8.dev/blog/fast-async#fn2

Maybe something like .footnote-item:target { background: lightyellow; }?

Maybe we need a glossary page with linkable quick explanations of common V8 concepts, such as "Smi".

This seems like a Good First Bug for a new team member ;)

https://twitter.com/Vjeux/status/1044814750838923269

There are two weird things on safari iOS 1) can you do something about the fake scroll for the twitter list that doesn’t have inertia? 2) there’s a weird issue where hover on the bottom links being triggered when scrolling.