This follows the same pattern as using chruby
, which is quite nice. Configured to autoload from .node-version
.
https://github.com/tkareine/chnode https://github.com/nodenv/node-build
- List available Node versions:
chnode
This follows the same pattern as using chruby
, which is quite nice. Configured to autoload from .node-version
.
https://github.com/tkareine/chnode https://github.com/nodenv/node-build
chnode
When Xcode is upgraded between major versions (for example 14 to 15), the whole compiler toolchain is upgraded along with support for the new platforms targeted. Sometimes this causes problems, like when deprecated APIs are finally removed.
These changes always happen around significant operating system releases, like when a new version of iOS is released towards the end of September. A good short-term solution is to install the old version of Xcode alongside the current one.
/Applications
, but with a name matching the version, e.g.: Xcode 13.4.1.app
I'd been trying to mock react-native-device-info
differently per test, so that I could explore setting a more useful User-Agent based on the platform it was running on. But Jest doesn't make doing this particularly very easy, at least not until recently:
We can use [jest.mocked
][1] to replace the implementation inside the it
:
import { getVersion } from 'react-native-device-info'
<html> | |
<head> | |
<script> | |
const webSocket = new WebSocket("ws://localhost:4283/ws"); | |
webSocket.onmessage = (event) => { | |
console.log(event.data); | |
} | |
window.webSocket = webSocket; |
# jump into the Homebrew repo
cd /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core
# find the sha to check out
git log master -- Formula/packer.rb
# uninstall the current version
HOMEBREW_NO_AUTO_UPDATE=1 brew uninstall packer
# check out the version, not allowing update
Checking a certificate will work is a bit of an awkward one to solve, but a built-in tool will do it:
PS> Set-Location "C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\IDE\CommonExtensions\Microsoft\TailoredProjectServices\"
PS> .\VSCertificateChecker.exe -f "C:\Users\NickCharlton\Documents\Certificates\DevelopmentTesting.pfx" -t msix
The file ALBAIKDevelopmentTesting.pfx is password-protected.
Enter password: ************************
Certificate Details:
Private Key Found: True
Testing file uploads in ActiveStorage is a little awkward. Fortunately, fixtures comes to the rescue and we can provide a file to be passed through to the parameters. This works across model and system/feature specs.
In your factory, you might define it like:
factory :document do
name { "Example File" }