⌘T | go to file |
⌘⌃P | go to project |
⌘R | go to methods |
⌃G | go to line |
⌘KB | toggle side bar |
⌘⇧P | command prompt |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
@charset "utf-8"; | |
html, body, body div, span, object, iframe, h1, h2, h3, h4, h5, h6, p, blockquote, pre, abbr, address, cite, code, del, dfn, em, img, ins, kbd, q, samp, small, strong, sub, sup, var, b, i, dl, dt, dd, ol, ul, li, fieldset, form, label, legend, table, caption, tbody, tfoot, thead, tr, th, td, article, aside, canvas, details, figcaption, figure, footer, header, hgroup, menu, nav, section, summary, time, mark, audio, video | |
{ margin: 0; padding: 0; border: 0; font-size: 100%; vertical-align: baseline; } | |
article, aside, details, figcaption, figure, footer, header, hgroup, menu, nav, section | |
{ display: block } | |
blockquote, q { quotes: none } |
After months of discussions in a dedicated group, it's clear to me NodeJS is still stuck in finding a way to deliver native ESM to its users.
The "usual few" won't hear anything different from .mjs
, but .mjs
has been demonstrated to be not a solution neither.
Following few cases not covered by .mjs
:
- evaluation of any string, via CLI, or on demand, where there is no extension
- tools that convert their syntax into JS, since it always worked to date (thanks to transpilers, bundlers, and loaders)