node --help --v8-options | grep -B 1 -A 1 max-old-space
type: bool default: false
--max-old-space-size (max size of the old space (in Mbytes))
type: size_t default: 0
Official Blogpost: https://sass-lang.com/blog/the-module-system-is-launched
Release: https://github.com/sass/dart-sass/releases/tag/1.23.0
#Using the sass-migrator in monorepo
// @use "../../../package/browser/css/file"; // alternative solution
@use "~package/browser/css/file";
Calling the migrator in the root directory, which is the same directory of packages/node_modules
and node_modules
will only find
{"version":1,"resource":"file:///h%3A/Digital-Clock-main/Digital-Clock-main/script.js","entries":[{"id":"m8wb.js","timestamp":1662637426203},{"id":"kcQL.js","source":"undoRedo.source","timestamp":1662637430965}]} |
{ | |
// Place your global snippets here. Each snippet is defined under a snippet name and has a scope, prefix, body and | |
// description. Add comma separated ids of the languages where the snippet is applicable in the scope field. If scope | |
// is left empty or omitted, the snippet gets applied to all languages. The prefix is what is | |
// used to trigger the snippet and the body will be expanded and inserted. Possible variables are: | |
// $1, $2 for tab stops, $0 for the final cursor position, and ${1:label}, ${2:another} for placeholders. | |
// Placeholders with the same ids are connected. | |
// Example: | |
// "Print to console": { | |
// "scope": "javascript,typescript", |
(function () { | |
"use strict"; | |
const table = document.querySelector("table"); | |
if (table) { | |
const thead = table.querySelector("thead"); | |
const tbody = table.querySelector("tbody"); | |
// create "Path" header column |
This is something a think about a lot. I a while ago I browsed the Pure ESM package gist by Sindresorhus and there's one point When should I use a default export or named exports?.
He suggests:
My general rule is that if something exports a single main thing, it should be a default export.
There's also this:
Why use default exports at all? Simplify usage: Having a default export simplifies import when the person importing the module just wants the obvious thing from there. There’s simply less syntax and typing to do.
#!/usr/bin/env node | |
const { readdir, writeFile } = require("fs"); | |
const { promisify } = require("util"); | |
function createDirEntry(dir) { | |
return { name: dir, path: `packages/node_modules/${dir}` }; | |
} | |
function createProjectCodeWorkspaceContents(dirs) { |
# EditorConfig is awesome: https://editorconfig.org/ | |
root = true | |
[*] | |
charset = utf-8 | |
indent_style = space | |
end_of_line = lf | |
indent_size = 2 | |
insert_final_newline = true |