If you are reading this, you probably tried to write code like this
test "testing session" do
build_conn()
|> put_session(:user_id, 234)
|> get("/")
...
end
And got this exception:
var gulp = require('gulp') | |
var browserify = require('browserify') | |
var babelify = require('babelify') | |
var source = require('vinyl-source-stream') | |
gulp.task('build', () => { | |
// our js lives in main.js, so its our source | |
var b = browserify('main.js') | |
b.transform(babelify, {presets: ['es2015', 'react']}) |
If you are reading this, you probably tried to write code like this
test "testing session" do
build_conn()
|> put_session(:user_id, 234)
|> get("/")
...
end
And got this exception:
#!bin/bash | |
for i in $( ls test ); do | |
npx mocha test/$i &> /dev/null | |
if [[ $? != 0 ]]; then | |
echo $i | |
fi | |
done |
const nock = require('nock'); | |
const path = require('path'); | |
nock.back.fixtures = path.resolve(`${__dirname}/fixtures/nockback/`); | |
nock.back.setMode('lockdown'); // change to 'record' to make new recordings | |
const allowLocalhost = () => { nock.enableNetConnect('127.0.0.1'); }; | |
const filterLocalhost = (reqs) => { | |
const localhost = /http:\/\/127\.0\.0\.1.*/; | |
return reqs.filter(r => !localhost.test(r.scope)); |
(pr/2853)$ npm run grunt --quiet | |
> p5@0.6.1 grunt /Users/evma/src/p5.js | |
> grunt | |
Running "yuidoc:prod" (yuidoc) task | |
Failed to find lines for { name: 'Shape', | |
submodules: | |
{ '2D Primitives': 1, | |
Curves: 1, |
You will need to install these tools on your machine:
There are two approaches to installing Node.js, manual and managed. If you're not sure which route to go, we recommend the managed route, but do whatever makes the most sense for your development process!
ffmpeg -i screen.mov -pix_fmt rgb8 -r 8 -vf scale=-1:640 my-gif.gif |
This is a recipe for teaching new coders how to contribute with open source projects. It also serves as a practice for validating feelings of uncertainty that learners often and shows them how these feelings can be fertile ground for improvements to the open source project and prompting larger conversations amongst other community members of the project.
In open source projects there is often a power dynamic between maintainers and newcomers where maintainers decide what is important and newcomers obey. Open source doesn’t have to be like this. As someone who helps maintain p5.js, I learn from newcomers often! Newcomers are experts on how easy it is to learn a tool and often have other unique and valuable perspectives to share.
This recipe was adapted from an assignment I created for the p5.js Approachability Lab, which took place in 2019 at UCLA under the advisement of Lauren McCarthy and was based on prior workshops