- To deploy it run
vercel
orvc
, or link the project to GitHub and rungit push
. - Do note
index.html
needs to be inside a folder calledpublic/
- Docs:
#!/usr/bin/env bash | |
function p() { | |
jq -n \ | |
--arg content "$*" \ | |
'{ | |
"model": "pplx-7b-online", | |
"messages": [ | |
{ | |
"role": "system", | |
"content": "Be precise and concise." |
<!DOCTYPE html> | |
<html> | |
<head> | |
<title>Next level UX</title> | |
<meta charset="UTF-8" /> | |
</head> | |
<body> | |
<p> | |
<label> |
const raw = require('raw-socket'); | |
const ip = require('ip'); | |
var options = { | |
protocol: raw.Protocol.ICMP | |
}; | |
const sourceIp = '127.0.0.1'; | |
const targetIp = '127.0.0.1'; |
With the release of Node 6.0.0, the surface of code that needs transpilation to use ES6 features has been reduced very dramatically.
This is what my current workflow looks like to set up a minimalistic and fast microservice using micro and async
+ await
.
Since Twitter doesn't have an edit button, it's a suitable host for JavaScript modules.
Source tweet: https://twitter.com/rauchg/status/712799807073419264
const leftPad = await requireFromTwitter('712799807073419264');
The following guide will show you how to deploy a simple microservice written in JavaScript using 𝚫 now.
It uses Open Source tools that are widely available, tested and understood:
- Node.JS
- NPM
- Express
After publishing my article on ECMAScript 6, some have reached out to ask how I exactly I make it all work.
I refrained from including these details on the original post because they're subject to immiment obsoletion. These tools are changing and evolving quickly, and some of these instructions are likely to become outdated in the coming months or even weeks.
When evaluating the available transpilers, I decided to use 6to5, which has recently been renamed to Babel. I chose it based on:
-
History of Realtime - @metajack
-
Realtime Insights - @guille
https://speakerdeck.com/rauchg/io-insights -
Making DISQUS Realtime - @NorthIsUp
dotjs userscript for visualizing package.json
files (if present) underneath the tree view.
Very useful for navigating Node.JS projects