| version: '2.2' | |
| networks: | |
| traefik: | |
| external: true | |
| guacamole: | |
| external: true | |
| services: | |
| guacamole: |
| //@flow | |
| export type Tree = { | |
| /*::+*/ id: ID, | |
| /*::+*/ kind: 'tree', | |
| /*::+*/ refs: Array<Tree>, | |
| /*::+*/ head: Array<StepValue>, | |
| /*::+*/ tail: Array<Tree>, | |
| /*::+*/ config: { | |
| runInBand: boolean, | |
| }, |
todo: create tool which could get diffs of stack traces and vars values to have easier debugging experience Especially, when you compare similar cases and one of them NOT WORKING!
- remove fucking "use strict";
sed -i -e 's|use strict|LoL|g' dist/davinciDesigner*.js
- for each function from call stack execute
| #!/bin/bash | |
| sed -i -e 's|throw error;|console.error(error);|g' node_modules/flow-runtime/dist/flow-runtime.umd.js |
| { | |
| "presets": [ | |
| "env", | |
| "stage-3" | |
| ] | |
| } |
With the addition of ES modules, there's now no fewer than 24 ways to load your JS code: (inline|not inline) x (defer|no defer) x (async|no async) x (type=text/javascript | type=module | nomodule) -- and each of them is subtly different.
This document is a comparison of various ways the <script> tags in HTML are processed depending on the attributes set.
If you ever wondered when to use inline <script async type="module"> and when <script nomodule defer src="...">, you're in the good place!
Note that this article is about <script>s inserted in the HTML; the behavior of <script>s inserted at runtime is slightly different - see Deep dive into the murky waters of script loading by Jake Archibald (2013)
| { | |
| "name": "tf-js", | |
| "version": "1.0.0", | |
| "main": "script.js", | |
| "license": "MIT", | |
| "dependencies": { | |
| "@tensorflow-models/mobilenet": "^0.2.2", | |
| "@tensorflow/tfjs": "^0.12.3", | |
| "@tensorflow/tfjs-node": "^0.1.9", | |
| "jpeg-js": "^0.3.4" |
16.06.2022
Дима Zerobias
01.03.2022
⛴➡️🍆