- GET Requests
- POST/PUT Requests
You are looking at the most important, and most abundant thing on the web. You can't see it, unfortunately, because it's very small… aaaaand it's invisible — so having a magnifying glass doesn't really help here. But still.
I'm talking, of course, about U+0020
; not to be confused with the band U2, who are just as ubiquitous, but far less useful.
This unicode point, representing the humble space character, is between every word, in every run of text, on every page of the web. And it has a very special characteristic: it's not sticky like glue. If two words are neighbors but there's not enough room for both of them, the space will free the second word to wrap around and start a new line.
Before getting into flexible containers, viewport meta tags, and @media
breakpoints this humble character is what makes the web fundamentally 'responsive'. That is: able to change the layout of its content to suit different devices, contexts, and settings. Browser text does this automa
@Component({ | |
templateUrl: './login-page.component.html' | |
}) | |
export class LoginPageComponent { | |
loginForm = new FormGroup({ | |
email: new FormControl('', Validators.required), | |
password: new FormControl('', Validators.required) | |
}); | |
error: string | null = null; |
#add 'node_modules' to .gitignore file | |
git rm -r --cached node_modules | |
git commit -m 'Remove the now ignored directory node_modules' | |
git push origin master |
import requests | |
import json | |
#### | |
# inputs | |
#### | |
username = '' | |
# from https://github.com/user/settings/tokens | |
token = '' |
import fs from 'fs' | |
import { makeExecutableSchema } from 'graphql-tools' | |
import { graphql } from 'graphql' | |
// the actual resolvers | |
import resolvers from '../src/resolvers' | |
// the mock service | |
import mockMovieService from './mocks/mockMovieService' | |
// a nice structure for test cases | |
// found at https://hackernoon.com/extensive-graphql-testing-57e8760f1c25 |
When you create a npm package, remember it might be used in a browser or a server, or even a command line utility… For each package you create, please pay attention at what it will be used for:
- Is it going to be used as a dependency to a nodejs application that is not bundled? (e.g. command line utilities)
- Is it going to be used as a dependency to a nodejs application that is bundled? (e.g. AWS Lambdas)
- Is it going to be used as a dependency to a browser application (always bundled)?.
- In cases 2) and 3) you want to allow for tree shaking.
- In cases 1) and 2) you want to benefit from the "ES6"/"ES next" features supported natively by nodejs.
- In case 3) you also want to benefit from the native support of "ES6" from your browser.