Just because I think it's simpler, faster, and I want to encourage people to use it :-)

Hello,

Thank you for the workshop. I'm excited to get started. I'm hoping to get some help with the following error on initial setup:

$ yarn -v
n1.7.0
$ node -v
v6.14.2
$ yarn run setup
yarn run v1.7.0
$ node ./scripts/verify && node ./scripts/install && npm run validate && node ./scripts/autofill-feedback-email
/code/sandbox/es6-workshop/scripts/verify.js:22
    )
    ^

SyntaxError: Unexpected token )
    at createScript (vm.js:56:10)
    at Object.runInThisContext (vm.js:97:10)
    at Module._compile (module.js:549:28)
    at Object.Module._extensions..js (module.js:586:10)
    at Module.load (module.js:494:32)
    at tryModuleLoad (module.js:453:12)
    at Function.Module._load (module.js:445:3)
    at Module.runMain (module.js:611:10)
    at run (bootstrap_node.js:394:7)
    at startup (bootstrap_node.js:160:9)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Something like the "precommit" script in package.json

"prepush": "yarn setup"

Would this be a desired feature, to locally run the tests and lint before pushing?

A use-case I can think of is to not have to wait till Travis gets back to the contributor that there is a minor lint violation.

Because we test on it but don't show a quiz about it first.

I was running my first test on the first exercise and got a syntax error:

$ yarn test:changed
yarn test:changed v0.19.1
$ npm run test --silent -- --onlyChanged
 FAIL  exercises/01_block-scoping.test.js
  ● Test suite failed to run

    SyntaxError: Unexpected token {

      at transformAndBuildScript (node_modules/jest-runtime/build/transform.js:320:12)
      at process._tickCallback (node.js:369:9)

Test Suites: 1 failed, 1 total
Tests:       0 total
Snapshots:   0 total
Time:        0.729s
Ran all test suites related to changed files.
error Command failed with exit code 1.

The file itself definetely has no syntax errors, i can attach it if it helps.
Thanks!

hi

I followed the setup process as described but when I run an individual quiz file I get this:

(function (exports, require, module, __filename, __dirname) { import log from './pretty-log' ^^^^^^ SyntaxError: Unexpected token import at Object.exports.runInThisContext (vm.js:73:16) at Module._compile (module.js:543:28) at Object.Module._extensions..js (module.js:580:10) at Module.load (module.js:488:32) at tryModuleLoad (module.js:447:12) at Function.Module._load (module.js:439:3) at Module.runMain (module.js:605:10) at run (bootstrap_node.js:418:7) at startup (bootstrap_node.js:139:9) at bootstrap_node.js:533:3

It might just be my machine of something...

Thanks

Node @ 7.5.0
yarn @ 0.19
npm @ 4.1.2

Now that we have Node v6, we can use Proxies which is pretty legit. Let's make an example of this! Some examples here

I run yarn start and go into the interactive mode.
When I run this function. I think it should throw an error about the reference due to let and const, but it did not.

Is this something wrong with the settings in this project about babel?

I could use some help coming up with ideas for extra credit tests!

I recorded a video about how to do this:

Please also check the Contributing guidelines. Thanks for your help!

I added a quizzes directory and intend on adding a few quiz functions for every concept to be used before/while teaching the concept. If anyone wants to help make those, please do! I recorded this video explaining how it works and stuff!

When running the command yarn quiz or npm run quiz, it's rerunning only on the first file change for this file.

After that, it's been ignoring all file changes on the file. However, changes in other files detected
And this is happening only for one file, 12_maps.js.

I tested the chokidar regex from run.js, which is *_*.js under quizzes directory.

I tested on two machines. On my laptop, I faced same issue with Atom and VSCode embedded terminals.

I have reproduced the issue on Cloud9. You can view the issue live here.

Have also posted in the gitter chatroom.

When running yarn run test:watch, there is no option to run in "only changed" mode, i.e. no o option. This makes me wonder why Jest decided to remove this option in the interactive dialog; the option can still be passed as an option to Jest CLI.

Anyway, the "How To Run Tests" needs to be updated.

Thanks a lot for this great workshop 😄

EDIT: I think Jest runs in "only changed" mode by default, i.e. no need to press o anymore.

const defaultObj = {
  name: 'Aaron',
  age: 35,
  favoriteBand: 'Queen'
};

function myFunction({name = 'Aaron', age = 35, favoriteBand = 'Queen'} = defaultObj) {
  expect(name).to.exist;
  expect(age).to.exist;
  expect(favoriteBand).to.exist;
}

myFunction();

But defaultObj is actually redundant! If you just set it to {}, it still works. As best as I can wrap my head around it:

1. Default parameter replacement: myFunction() → myFunction({})
2. Destructuring: name = {}.name; ... all of which are undefined
3. Default parameters, again! name = name === undefined ? 'Aaron' : name; ... which effectively rebuilds defaultObj.

This is insane. WebAssembly can't come soon enough. :)

Because when someone forks this repo to contribute stuff, it becomes a fork of the original repo making it hard to contribute to this repo. This repo has diverted significantly from the original repo anyway and I will leave the gratitude in the README and leave the commits as they are, so I think it'll be fine.

👋 stars, forks, and watchers :-(