If you have an issue comment / PR description on GitHub, it doesn't automatically get anchors / IDs that you could link to:
What I like to do is to add a visible # character like this:
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| <!doctype html> | |
| <html> | |
| <head> | |
| <title>Froala with Webpack</title> | |
| </head> | |
| <body> | |
| <div id="editor"></div> |
remarkablemark
/ README.md
Last active
May 23, 2024 20:32
How to mock `window.location.reload` in Jest and jsdom: https://remarkablemark.org/blog/2018/11/17/mock-window-location/
gricard
/ webpack4upgrade.md
Last active
February 29, 2024 20:23
Just some notes about my attempt to upgrade to webpack 4
If you enjoyed reading this, I'm intending to do more blogging like this over here: https://cdgd.tech
This is not a complaint about Webpack or v4 in any way. This is just a record of my process trying it out so I could provide feedback to the webpack team
Hmm... I don't see any docs for 4.0 on https://webpack.js.org. I guess I'll just wing it.
All I need to do is npm i -D webpack@next, right?
+ webpack@4.0.0-beta.2
robertgonzales
/ Frame.js
Created
December 12, 2017 03:03
Use React portals to render inside shadow dom and iframes
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| class Frame extends Component { | |
| componentDidMount() { | |
| this.iframeHead = this.node.contentDocument.head | |
| this.iframeRoot = this.node.contentDocument.body | |
| this.forceUpdate() | |
| } | |
| render() { | |
| const { children, head, ...rest } = this.props | |
| return ( |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| //@flow | |
| import React, { Component } from 'react' | |
| import type { ElementRef } from 'react' | |
| type Props = { src: string, alt: string } | |
| type State = { source?: string } | |
| export default class LazyImage extends Component<Props, State> { | |
| state = {} |
480
/ gist:3b41f449686a089f34edb45d00672f28
Last active
July 3, 2024 03:59
MacOS X + oh my zsh + powerline fonts + visual studio code terminal settings
Thank you everybody, Your comments makes it better
sh -c "$(curl -fsSL https://raw.github.com/ohmyzsh/ohmyzsh/master/tools/install.sh)"
morewry
/ monorepo-tool-comparison.md
Last active
May 11, 2022 08:54
Comparison of Monorepo Tools For Web Client / Front End Projects (That Probably Use HTML, CSS, and JS)
I made a list of 20 things I might want out of a monorepo tool for a Design System to use as a basis for comparing some of the options including Lerna, Northbrook, and Rush.
fokusferit
/ enzyme_render_diffs.md
Last active
June 18, 2024 11:27
Difference between Shallow, Mount and render of Enzyme
nikolasburk
/ graphql-vs-firebase.md
Created
April 2, 2017 14:48
With the variety of server-side technologies today, developers have a lot of choices when it comes to deciding what kind of backend to use for their next application.
In this article, we want to explore the differences between GraphQL and Firebase, two very popular server-side technologies.
Before diving into technical details, let's create some perspective on the two technologies and where they're coming from.
NewerOlder