If your Mac is out-of-order or you otherwise cannot download macOS from the App Store, you can still create a bootable OS X recovery USB, and you can use that to create an Installer USB.
The downloads used in this process are legal and freely avaliable - including disk images directly from Apple's IT support pages, and open source utilities for extracting and converting pkg, dmg, and HFS+.
| #!/bin/sh | |
| # SetDNS.sh | |
| # | |
| # | |
| # Created by David Kittell on 6/14/19. | |
| # | |
| # Variables - Start | |
| sExternalIPService="http://dns.kittell.net/ip.php" |
| import React, { useState, useEffect } from 'react' | |
| import PropTypes from 'prop-types' | |
| import { checkIsAuthenticated, authSignUp, authLogin, authLogout } from '../../services/auth' | |
| export const AuthContext = React.createContext({}) | |
| export default function Auth({ children }) { | |
| const [isAuthenticated, setIsAuthenticated] = useState(false) | |
| const [isLoading, setIsLoading] = useState(true) |
With the addition of ES modules, there's now no fewer than 24 ways to load your JS code: (inline|not inline) x (defer|no defer) x (async|no async) x (type=text/javascript | type=module | nomodule) -- and each of them is subtly different.
This document is a comparison of various ways the <script> tags in HTML are processed depending on the attributes set.
If you ever wondered when to use inline <script async type="module"> and when <script nomodule defer src="...">, you're in the good place!
Note that this article is about <script>s inserted in the HTML; the behavior of <script>s inserted at runtime is slightly different - see Deep dive into the murky waters of script loading by Jake Archibald (2013)
React recently introduced an experimental profiler API. After discussing this API with several teams at Facebook, one common piece of feedback was that the performance information would be more useful if it could be associated with the events that caused the application to render (e.g. button click, XHR response). Tracing these events (or "interactions") would enable more powerful tooling to be built around the timing information, capable of answering questions like "What caused this really slow commit?" or "How long does it typically take for this interaction to update the DOM?".
With version 16.4.3, React added experimental support for this tracing by way of a new NPM package, scheduler. However the public API for this package is not yet finalized and will likely change with upcoming minor releases, so it should be used with caution.
| // EmailInput wraps an HTML `input` and adds some app-specific styling. | |
| const EmailInput = React.forwardRef((props, ref) => ( | |
| <input ref={ref} {...props} type="email" className="AppEmailInput" /> | |
| )); | |
| class App extends Component { | |
| emailRef = React.createRef(); | |
| render() { | |
| return ( |
| // you can write to stdout for debugging purposes, e.g. | |
| // console.log('this is a debug message'); | |
| function solution(A) { | |
| // write your code in JavaScript (Node.js 8.9.4) | |
| let tmp = [] | |
| for (let i = 0; i < A.length; i++) { | |
| if (0 <= A[i]) { | |
| tmp[A[i]] = true |
API_CALL_REQUEST описывает что мы начинаем процесс получения данных с API
API_CALL_SUCCESS описывает что store успешно получил данные и процесс получения данных завершен
API_CALL_FAILURE описывает что API вызов завершился ошибкой
