| { | |
| "name": "workshop-computer-validator", | |
| "version": "1.0.0", | |
| "description": "I use this to validate people's computers have the proper versions of node and npm installed for a workshop", | |
| "bin": "./validate-system.js", | |
| "dependencies": { | |
| "semver": "7.1.3" | |
| } | |
| } |
| angular.module('myMdl', []).config(['$httpProvider', function($httpProvider) { | |
| $httpProvider.responseInterceptors.push([ | |
| '$q', '$templateCache', 'activeProfile', | |
| function($q, $templateCache, activeProfile) { | |
| // Keep track which HTML templates have already been modified. | |
| var modifiedTemplates = {}; | |
| // Tests if there are any keep/omit attributes. | |
| var HAS_FLAGS_EXP = /data-(keep|omit)/; |
| /** | |
| * In our app, we have a few middleware that generate a string of HTML. | |
| * On occassion it's fine to just use dangerouslySetInnerHTML directly for | |
| * those, but that requires that you have a host node for the innerHTML. | |
| * | |
| * In certain scenarios (like tags in <head />), there's HTML that we need | |
| * to insert directly where it is. This component enables that because | |
| * we replace <raw-text> and </raw-text> with empty strings. Effectively | |
| * making whatever's between <raw-text> and </raw-text> inlined in place. | |
| * |
Sublime Text 2 ships with a CLI called subl (why not "sublime", go figure). This utility is hidden in the following folder (assuming you installed Sublime in /Applications like normal folk. If this following line opens Sublime Text for you, then bingo, you're ready.
open /Applications/Sublime\ Text\ 2.app/Contents/SharedSupport/bin/subl
You can find more (official) details about subl here: http://www.sublimetext.com/docs/2/osx_command_line.html
| import { useState, useEffect, useCallback } from 'react' | |
| function usePromise(createPromise) { | |
| const [error, setError] = useState() | |
| const [value, setValue] = useState() | |
| useEffect(() => { | |
| let current = true | |
| createPromise().then( |
| node_modules |
I heard some points of criticism to how React deals with reactivity and it's focus on "purity". It's interesting because there are really two approaches evolving. There's a mutable + change tracking approach and there's an immutability + referential equality testing approach. It's difficult to mix and match them when you build new features on top. So that's why React has been pushing a bit harder on immutability lately to be able to build on top of it. Both have various tradeoffs but others are doing good research in other areas, so we've decided to focus on this direction and see where it leads us.
I did want to address a few points that I didn't see get enough consideration around the tradeoffs. So here's a small brain dump.
"Compiled output results in smaller apps" - E.g. Svelte apps start smaller but the compiler output is 3-4x larger per component than the equivalent VDOM approach. This is mostly due to the code that is usually shared in the VDOM "VM" needs to be inlined into each component. The tr
| // please check https://docs.netlify.com/configure-builds/environment-variables/#declare-variables for most up to date info | |
| // this was created before those docs existed | |
| process.env = { | |
| /** | |
| * | |
| * AUTOMATICALLY SET BY NETLIFY. IMMUTABLE! | |
| * docs: https://www.netlify.com/docs/continuous-deployment/#environment-variables | |
| * | |
| */ |
Remix Deferred is currently implemented on top of React's Suspense model but is not limited to React. This will be a quick dive into how "promise over the wire" is accomplished.
It isn't rocket science, but a quick recap of how frameworks such as react do SSR:
| if (req.method === 'OPTIONS') { | |
| console.log('!OPTIONS'); | |
| var headers = {}; | |
| // IE8 does not allow domains to be specified, just the * | |
| // headers["Access-Control-Allow-Origin"] = req.headers.origin; | |
| headers["Access-Control-Allow-Origin"] = "*"; | |
| headers["Access-Control-Allow-Methods"] = "POST, GET, PUT, DELETE, OPTIONS"; | |
| headers["Access-Control-Allow-Credentials"] = false; | |
| headers["Access-Control-Max-Age"] = '86400'; // 24 hours | |
| headers["Access-Control-Allow-Headers"] = "X-Requested-With, X-HTTP-Method-Override, Content-Type, Accept"; |