Não use UUID
como PK nas tabelas do seu banco de dados.
logging: { | |
// Only console logging is currently supported | |
console: { | |
level: "trace", | |
metrics: false, | |
audit: false | |
}, | |
loki: { | |
level:'trace', | |
metrics:false, |
// https://www.meziantou.net/how-to-use-csharp-8-indices-and-ranges-in-dotnet-standard-2-0-and-dotn.htm |
$remoteport = bash.exe -c "ifconfig eth0 | grep 'inet '" | |
$found = $remoteport -match '\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}'; | |
if( $found ){ | |
$remoteport = $matches[0]; | |
} else{ | |
echo "The Script Exited, the ip address of WSL 2 cannot be found"; | |
exit; | |
} |
Welcome to step by step hands-on guide to setup webpack in your upcoming typescript project. Please follow the steps and you should be able to create your own webpack project. Please download the source code from github.
You will learn below things:
- ✅Create a Typescript node.js project.
- ✅Install Dependencies with webpack & typescripts.
- ✅Use Webpack CLI to crate
webpack.config.js
file and modify webpack.config.js based on our need.
{ | |
"version": "0.2.0", | |
"configurations": [ | |
{ | |
"name": "Example", | |
"type": "node", | |
"request": "launch", | |
"runtimeExecutable": "node", | |
"runtimeArgs": ["--nolazy", "-r", "ts-node/register/transpile-only"], |
My current editor of choice for all things related to Javascript and Node is VS Code, which I highly recommend. The other day I needed to hunt down a bug in one of my tests written in ES6, which at time of writing is not fully supported in Node. Shortly after, I found myself down the rabbit hole of debugging in VS Code and realized this isn't as straightforward as I thought initially. This short post summarizes the steps I took to make debugging ES6 in VS Code frictionless.
My first approach was a launch configuration in launch.json
mimicking tape -r babel-register ./path/to/testfile.js
with babel configured to create inline sourcemaps in my package.json
. The debugging started but breakpoints and stepping through the code in VS Code were a complete mess. Apparently, ad-hoc transpilation via babel-require-hook and inline sourcemaps do not work in VS Code. The same result for
attaching (instead of launch) to `babel-node
{ | |
"presets": ["es2015"], | |
"plugins": ["transform-async-to-generator"] | |
} |
Windows Registry Editor Version 5.00 | |
; | |
; Adds 'Open in Atom' to context menu (when you right click) in Windows Explorer. | |
; | |
; Based on https://github.com/Zren/atom-windows-context-menu. It didn't work | |
; https://github.com/Zren/atom-windows-context-menu/issues/1. | |
; | |
; Save this file to disk with a .reg extension. Replace C:\\Atom\\atom.exe with | |
; the path to the atom executable on your machine. |
using System.IO; | |
using System.Text; | |
using System.Xml; | |
namespace XMLMinifier | |
{ | |
/// <summary> | |
/// Config object for the XML minifier. | |
/// </summary> | |
public class XMLMinifierSettings |