This is a CFP for ReactiveConf open call for lightning talks. If you'd like to see this talk become a reality, please ⭐️ star this gist. #ReactiveConf
If you're on your phone, please request the desktop site to star this gist 😇
This is a CFP for ReactiveConf open call for lightning talks. If you'd like to see this talk become a reality, please ⭐️ star this gist. #ReactiveConf
If you're on your phone, please request the desktop site to star this gist 😇
This is a CFP for ReactiveConf open call for lightning talks. If you'd like to see this talk become a reality, please ⭐️ star this gist. #ReactiveConf
This proposal is not longer active. Context: https://twitter.com/siddharthkp/status/909818777314902016
{ | |
"apps": [{ | |
"name": "Application", | |
"exec_interpreter": "./node_modules/babel-cli/bin/babel-node.js", | |
"script": "./bin/www", | |
"args": [], | |
"watch": ["public", "package.json", "pm2.development.json"], | |
"ignore_watch": ["public"], | |
"watch_options": { | |
"persistent": true, |
Seen a few tweets on this. I want to dispel some FUD.
Node is probably going to introduce a new file extension for JavaScript modules, .mjs
. The reasons for this are long and perilous, and trying to summarize the discussion that led to it is maddening. The short version is that ES6 modules have different semantics from existing scripts, and need to be executed differently. In browsers, this is done with <script type="module">
. In Node, this will be done by analyzing the file extension of the imported file.
I'll be honest: I don't love this solution! I was rooting for the TC39 counter-proposal. But I also understand the solution that the Node developers chose, and why they chose it.
The new file extension is a good enough solution. You can read the [draft spec](https://github.com/nodejs/node-eps/
NOTE: Sokra confirmed I had a misunderstanding, Webpack is still a static build tool and the below won't work. It's still a nice concept though...
With webpack 1, code splitting react-router routes is quite tedious. It requires us to repeat the getComponent
function over and over again. (See here for an explanation how it works with webpack 1)
Example:
<Router history={history}>
<Route
path="/"
function loadCSS( href, before, media){ | |
"use strict"; | |
// Arguments explained: | |
// `href` is the URL for your CSS file. | |
// `before` optionally defines the element we'll use as a reference for injecting our <link> | |
// By default, `before` uses the first <style> element in the page. | |
// However, since the order in which stylesheets are referenced matters, you might need a more specific location in your document. | |
// If so, pass a different reference element to the `before` argument and it'll insert before that instead | |
// note: `insertBefore` is used instead of `appendChild`, for safety re: http://www.paulirish.com/2011/surefire-dom-element-insertion/ | |
var ss = window.document.createElement( "link" ); |