slavafomin

Using TypeScript Node.js with native ESM

This reference guide shows how to configure a TypeScript Node.js project to work and compile to to native ESM.

Rationale

CommonJS module system was introduced by the Node.js developers due to the lack of the notion of "modules" in the original JavaScript (ECMAScript) language specification at that time. However, nowadays, ECMAScript has a standard module system called ESM — ECMAScript Modules, which is a part of the accepted standard. This way CommonJS could be considered vendor-specific and obsolete/legacy. Hopefully, TypeScript ecosystem now supports the "new" standard.

So the key benefits are:

slavafomin

import TonWeb from 'tonweb';

import {
  BatchLoadedHandler,
  getAddressTransactions,
  HttpErrorHandler,
  TransactionDiscoveredHandler,

} from './address-transactions';

pablodz

# [🟨OPTIONAL] Uninstall old docker versions
sudo apt-get remove docker docker-engine docker.io containerd runc
# Refresh latest version
sudo apt-get update
# Install pre-req
sudo apt-get install -y \
    apt-transport-https \
    ca-certificates \
    curl \
    gnupg \

slavafomin

# IDEA-based IDEs
/.idea/

# Build files
**/dist/

# Dependencies
**/node_modules/

# Temp files

bmaupin

ⓘ This list is not meant to be exhaustive and is not guaranteed to be maintained. See the comments for updates and alternative options.

(Items in bold indicate possible concerns)

	Keycloak	WSO2 Identity Server	Gluu	CAS	OpenAM	Shibboleth IdP
OpenID Connect/OAuth support	yes	yes	yes	yes	yes	yes
Multi-factor authentication	yes	yes	yes	yes	yes	yes
Admin UI	yes	yes	yes	yes	yes	no
OpenJDK support	yes	yes	partial²	yes

adcreare

Steps to publish a npm package to beta that won't be available via latest and won't auto install on ncu updates etc

1. Ensure any compile is run npm run dist etc
2. Modify version in package.json to the following format (match with existing verion numbers etc) "version": "0.1.120-beta.1" where beta.x is the number of those betas
3. Publish to npm npm publish --tag beta

There are two options for install:

• Always install beta with npm install packagename@beta
• Install specific version with npm install package@0.1.120-beta.1

miguelmota

version: 0.1
phases:
  install:
    commands:
      - apt-get update
      - apt-get install nodejs -y
      - gem install bundler
      - gem install middleman
  pre_build:
    commands:

slavafomin

const Metalsmith = require('metalsmith');
const inPlace = require('metalsmith-in-place');

Metalsmith(__dirname)
  .source('./src')
  .destination('./build')
  .use(inPlace({
    pattern: '**/*.njk',
    engineOptions: {

mort3za

# Generate a new pgp key: (better to use gpg2 instead of gpg in all below commands)
gpg --gen-key
# maybe you need some random work in your OS to generate a key. so run this command: `find ./* /home/username -type d | xargs grep some_random_string > /dev/null`

# check current keys:
gpg --list-secret-keys --keyid-format LONG

# See your gpg public key:
gpg --armor --export YOUR_KEY_ID
# YOUR_KEY_ID is the hash in front of `sec` in previous command. (for example sec 4096R/234FAA343232333 => key id is: 234FAA343232333)

bradwestfall

S3 Static Sites

⚠ This post is fairly old. I don't keep it up to date. Be sure to see comments where some people have posted updates

What this will cover

• Host a static website at S3
• Redirect www.website.com to website.com
• Website can be an SPA (requiring all requests to return index.html)
• Free AWS SSL certs
• Deployment with CDN invalidation