_stream_readable.js:749
    throw new Error('Cannot switch to old mode now.');
          ^
Error: Cannot switch to old mode now.
    at emitDataEvents (_stream_readable.js:749:11)
    at ReadStream.Readable.resume (_stream_readable.js:734:3)
    at showMenu (/Users/sethvincent/workspace/javascript-modules/nodeschool/javascripting/node_modules/workshopper-adventure/menu.js:90:17)
    at showMenu (/Users/sethvincent/workspace/javascript-modules/nodeschool/javascripting/node_modules/workshopper-adventure/exerciseMenu.js:29:10)
    at Adventure.printMenu (/Users/sethvincent/workspace/javascript-modules/nodeschool/javascripting/node_modules/workshopper-adventure/adventure.js:462:14)
    at Adventure.execute (/Users/sethvincent/workspace/javascript-modules/nodeschool/javascripting/node_modules/workshopper-adventure/adventure.js:203:8)
    at Object.<anonymous> (/Users/sethvincent/workspace/javascript-modules/nodeschool/javascripting/index.js:19:7)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)

Looks like it is related to process.stdin.pause() / process.stdin.resume() in the menu.js file of workshopper-adventure

I think it would be wise to choose one entry point for newcomers to ask questions. Can you reconsider changing the gitter link to redirect to nodeschool/discussions?

Really dig this!

However, there seems to be a bug.

The for-loop exercise indicates that the limit variable should equal 10.

Then when a user runs verify, it expects 45 instead of 10.

The user then has to change the limit variable o 45 to pass the validation.

If this is by design, my apologies.

Thanks!

javascripting now has i18n support thanks to @martinheidegger!

@a0viedo, @NgaNguyenDuy: we could potentially merge the translations you've been working on into this module to make things simpler. You can look at the additions made in the latest commits to see how the japanese translation works. let me know what you think!

run-content.js uses a child_process exec string to run solutions. Since it is possible for attempted solution paths to contain spaces, the path part of the exec string should be surrounded with double quotes.

For example, running javascripting verify C:\Users\TestUser\nodeschool test\introduction.js causes the following error:

Error: Command failed:
module.js:340
    throw err;
          ^
Error: Cannot find module 'C:\Users\TestUser\nodeschool'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:280:25)
    at Function.Module.runMain (module.js:497:10)
    at startup (node.js:119:16)
    at node.js:929:3

We should create troubleshooting_ko.md and troubleshooting_es.md files before doing the next npm release.

Currently I get this error when the verify command fails and I have a language selected that doesn't have a troubleshooting_xx.md file:

Error: ENOENT, no such file or directory '/Users/sethvincent/workspace/javascript-modules/nodeschool/javascripting/troubleshooting_es.md'

Original discussion here. I was reading the sentence in the nodeschool site and goes as follows:

The workshop runs their solution and checks if all requirements were satisfied. If any are wrong or missing the learner gets contextual feedback and they can try again.

And this is what it's displaying right now:

Not like any contextual feedback I've ever seen...Maybe we can encourage to try again?

Hello,

Upon running:

javascripting

on Ubuntu I get the following error:

/usr/bin/env: node: No such file or directory

I'm very new to Ubuntu and have never done Node.JS before, am I doing something wrong? The server is relatively new, I've installed telnet and ssh but not much else.

Console log - http://pastebin.com/n7ifVjGU

Thanks in advance,

Popey

Hi,

I followed the suggested commands for installing but even after installing the module 'javascripting'
fails to run as a global variable. The error I receive when attempting to run it as a global variable is "/usr/bin/env: node: No such file or directory".

After receiving this error I attempted to move the module to /usr/bin/env from the directory it installed in (usr/local/lib/node_modules/javascripting). Unfortunately, I was not able to move the files because /usr/bin/env is not a directory, rather it seems to be some sort of executable java file (usr/bin is a directory).

I am a bit lost and would love some advice on either how to install the module as a working global variable or whether there is another way to run the module without installing it as a global variable.

Thanks!

I cannot move on from this exercise...below are my code and the result I am getting. What am I doing wrong?

Thanks.

MY CODE:

var total = 0;
var limit = 10;

for (var i = 0; i < limit; i++) {
total =+ i;
};

console.log(total);

RESULT:

Solution

45

Your Attempt

9

Difference

945

hey this module rules so far!

I use the default white terminal style on macOS and it looks like this:

I hooked up http://npmjs.org/ansimd but it required me sending this PR stephenmathieson/node-ansimd#1

I think it would be best to disable syntax highlighting by default, but im not sure if the cli-md module can do that

if you like ansimd more I can send a PR once the upstream one lands

Node 4.2.1, Windows 7:

Official solutions aren't provided after running, for example: javascripting verify program.js. Wanted to give a heads up in case this is not a known issue at this time.

Here's an example of the output:

# PASS
Your solution to ROUNDING NUMBERS passed!

Here's the official solution in case you want to compare notes:

───────────────────────────────────────────────────────────────

# THAT NUMBER IS ROUNDED

 Yep, you just rounded the number 1.5 to 2. Good job.

 In the next challenge we will turn a number into a string.

 Run javascripting in the console to choose the next challenge.

───────────────────────────────────────────────────────────────

You say, "now we're going to learn about strings", but the next lesson is on variables.

https://github.com/sethvincent/javascripting/blob/master/problems/introduction/solution.md

hello,
I have for-loop.js which contains this:

var total = 0
var limit  = 10
for (var i = 0; i < limit; total += i) {
    total =+ i;
};
console.log(total);

Whenever I try to run javascripting verify for-loop.js, the terminal just hangs and provides no feedback. What did I do this time :) ?

Thx!

The main menu does not work when run with nodejs v4.0, only in version 0.12 and earlier.

can you guys tell me why i am seeing this error...
for the functions task even i copied the code from solutions but still I am seeing this error.
can u help me in fixing it

C:\Users\Desktop\node-school> javascripting verify functions.js

O-oh, something isn't working.

But don't panic!

Need help? Ask a question at: github.com/nodeschool/discussions/issues

hi, i'm new but it's not installing for some reason. I have node installed but when I type in javascripting after following the instructions, I get "-bash: javascripting: command not found". Thanks for the help!

This would be even cooler if it had an electron app to go along with it. 😎 Ps add me 👍

Installed node, installed javascripting, ran javascripting, got the blue menu, selected the first lesson and:

TypeError: Object #(Transform) has no method 'destroy'

followed by a traceback..
Any ideas?

Running 32 bit node.js on Win 7

There is a critical bug.

When I try to verify something, it throw error:

module.js:339
    throw err;
    ^

Error: Cannot find module './lib/footer.js'
    at Function.Module._resolveFilename (module.js:337:15)
    at Function.Module._load (module.js:287:25)
    at Module.require (module.js:366:17)
    at require (module.js:385:17)
    at Object.<anonymous> (/usr/lib/node_modules/javascripting/lib/problem.js:42:9)
    at /usr/lib/node_modules/javascripting/lib/compare-solution.js:27:7
    at /usr/lib/node_modules/javascripting/lib/run-solution.js:9:10
    at ChildProcess.exithandler (child_process.js:194:7)
    at emitTwo (events.js:87:13)
    at ChildProcess.emit (events.js:172:7)

UPD: I've tried to check out here e1101b2. All works fine here. So, maybe something goes wrong with @martinheidegger's commits.

Hello @sethvincent I am asking even though I wonder if its futile: Do you think its hard to change the system to workshopper. The reason why I asked is: It is quite some work to translate the content into various languages. Changing to workshopper would make it easier to translate javascripting to other languages.

If the user accidentally creates a file with the wrong name, the workshop produces the generic error "O-oh, something isn't working."

It should let the user know that the file being verified doesn't have the expected name (or doesn't exist).

As someone who has no previous JavaScript knowledge, the Scope problem is quite frustrating. Even though the introduction does a good job defining scope, I was not prepared to follow the code example.

Comments need to be added next to console.log to indicate that when we pass the argument within bar back to the function, var b = 2 will be ignored. I'm sure I haven't phrased that well, but it's a starting point.

Also, what purpose does the line foo(); // 4, 2, 48 serve? I understand that foo is the function's name, and the comments next to it are the values of these variables, but this statement is just sitting there. We need context. What would including foo(); at the end of this program do when we run it?

I also don't believe the IIFE section adds any relevant information to this problem. It is distracting.

Now moving on to the challenge, I don't understand why there is )(); after every closing }. I suppose that ties back to the foo(); in the example code, but I don't understand its usage.

I've started adding some example ones over here. I know it's pretty crude (those regexs are pretty horrible! :p). Just wanted to gauge peoples responses before I start adding more to all the other exercises and cleaning everything up.

Eg.

$ cat a.js
var pizza = 'pizza is alright';
pizza.replace("alright", "wonderful");
console.log(pizza);

$ javascripting verify a.js
Nearly there! The replace function returns a new string, so make sure you assign the result to a variable!
-------------------
# O-oh, something isn't working.
But don't panic!
-------------------
Need help? Ask a question at: github.com/nodeschool/discussions/issues

I feel providing the output from the submitted files in the terminal on failed (and maybe even on successful submissions) would be beneficial reinforcement. You can see where you might be going wrong. Perhaps at the very least provide somewhere in the Readme or elsewhere that running node filename.js in the terminal will print your output.

well, that or the messages you get on success about what you're going to do next are in the wrong order for those two exercises.

also there's an extraneous ` in the console.log instruction line in accessing array values.

Are you planning to publish a new version with the added translations any time soon?

I got reminded in nodeschool/discussions#700 that sometimes the problem occurs that people don't see the difference in their output. uppercase/lowercase etc. It might be good to check something like:

function normalise(string) {
   return string.replace(/\.|\!|\?|\s|/g, "").toLowerCase()
}

function isProbablyTypo(expectedAnswer, answer) {
   return normalise(expectedAnswer) === normalise(answer)
}

if (isProbablyTypo(expectedAnswer, answer)) {
   console.log("Looks like you did the right thing but maybe you had a typo in there. We are a little picky to make sure that you understood the question. Maybe you want to check for typos?")
}

In solarized dark theme certain text areas invisible. Maybe it is problem of the theme but this is rather annoying and the theme is quite popular. Possible workaround is with --no-colors.

Installed node and javascripting tutorial this mornig on Windows 8 machine:

$ node --version
v0.10.35

I then installed the current (v1.9.1) release of the javascripting tutorial from http://nodeschool.io/#workshopper-list using the command:

npm install -g javascripting

I created a file, introduction.js, with the contents:

console.log('hello');

I then ran the verify command, the the output was:

# O-oh, something isn't working.
# But don't panic!
-------------------
## Check your solution:
Solution
===================

Your Attempt
===================
hello

Difference
===================
hello

Checked in with the nodeschool discussion at https://gitter.im/nodeschool/discussions, and martin verified that this is a problem introduced in the v1.9.1 release. He had me revert to v1.9.0:

npm i [email protected] -g

And now the verification is working correctly:

$ javascripting verify introduction.js
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@@     YOUR SOLUTION IS CORRECT!     @@@
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
-------------------
# YOU DID IT!

Hello,

First of all, thanks for putting this together. I do appreciate it!

I've noticed that apostrophes in instructions are converted to '. I've tried hacking at this to find a solution, but was unsuccessful. I suspect it may even be with the cli-md module as double quotes are converted to " and so on.

If I can be of any help to resolve this, don't hesitate to let me know.

Thanks!

currently I get:

$ javascripting run foo.js 
ERROR: This problem doesn't have a .run function.

but it would be useful to have to help people debug, such as here nodeschool/discussions#640

This may soon be obsolete if you follow up on #125, but I noticed inconsistent spaces in the scope exercise:

Use your knowledge of the variables' scope and place the following code inside one of the functions in 'scope.js'
so the output is a: 1, b: 8,c: 6

console.log("a: "+a+", b: "+b+", c: "+c);

Is there or is there not supposed to be a space before c: 6? (That is a rhetorical question: I already did the exercise. ;)

Even with the For Loop section pulled up, I was not able to find my own solution to the Looping Through Arrays challenge. It wasn't clear to me what I should put for the variable and the condition, as well as how I should increment.

I didn't immediately pick up on the hint that I had to define the variable i in order for it to be used. I also thought something like i++ only worked on numerical values. I didn't understand how to use it on the string values of the pets array.

Once I reviewed the posted solution, I realized that an arbitrarily named counter variable is what is being incremented, which is represented here by the variable i. This value increases every time the loop repeats. As long as the numerical value of i is less than the number of positions in the pets array, every entry in the array is assigned to be the same value with an s added to the end of it.

I think we could phrase the Looping Through Arrays challenge in a way in which would have helped me come to these realizations without needing to pull up both the For Loop section and the solution. This challenge took much longer to understand than any of the other ones.

Install and run:

$ javascripting

Select the first adventure INTRODUCTION, fails with:

node: ../deps/uv/src/unix/stream.c:1174: uv_shutdown: Assertion `(stream->type == UV_TCP || stream->type == UV_NAMED_PIPE) && "uv_shutdown (unix) only supports uv_handle_t right now"' failed.
Aborted

Works fine with v0.12 though.

the arrows are not working or I do not know how...

migrated from nodeschool/discussions#760
/cc @closer76 @SomeoneWeird @a0viedo @martinheidegger

1. The example of this lesson is shown as:

   var n = 256;
   n.toString();

And it might lead to confusion, since .toString() won't modify n itself and this statement doesn't make much sense. Suggested to be:

   var n = 256;
   n = n.toString();

1. I tried the following code snippet for the chanllenge:

   var n = 128;
   n.toString();
   console.log(n);   // well, n is still a number, not a string
   

   and it passed the verification (which is wrong). I think the problem is the verification script checks the output only, and in this case, the output will always be 128 no matter n is a number or a string.

   I suggest to ask challengers to print out "the length of the string". If the challenger tries to use .length on a number, he or she will get "undefined".

After I do the installation:

npm install --global javascripting

Y try to run: javascripting in terminal

But terminal show me this error:

/usr/bin/env: node: No such file or directory

Some text is invisible in Windows when using PowerShell. Here is an example from array filtering

I'm pretty sure I've got the looping through arrays code right, but I'm getting this error (there's no way the solution is supposed to be 45 if we're trying to get the array values to be plural, right?)

$ javascripting verify looping-through-arrays.js
-------------------
# O-oh, something isn't working.

# But don't panic!

-------------------
## Check your solution:

Solution
===================

45


Your Attempt
===================

[ 'cats', 'dogs', 'rats' ]


Difference
===================

[ 'cats', 'dogs', 'rats' ]45

My code was:

File: looping-through-arrays.js                        

var pets = ['cat', 'dog', 'rat'];
for (var i = 0; i < 3; i++) {
  pets[i] = pets[i] + 's';
}
console.log(pets);

Am I crazy? Possibly crazy.

In instructions for Objects, the instructions for how to define pizza contain an extra comma:

var pizza = {
  toppings: ['cheese', 'sauce', 'pepperoni'],
  crust: 'deep dish',
  serves: 2, // <-- Extra comma causes failure
}

I want to contribute to with the scope lesson (in english) but I have some doubts i want to solve before creating a pull request.

Since the lesson would be new there are no translations for it, so when picking another language (ex. chinese) two things happen:

1. the scope lesson name in the main menu appears as "?zh-cn.exercise.SCOPE?"
2. when this option (scope lesson) is selected the program crashes

Is there any way to fix this or is it normal until the translations are provided?
in that case, should I do the pull request?

I'd like to get the translations released to npm, but it looks like there are a couple things we should settle first:

• #84 translate troubleshooting.md to ko & es
• #83 have an approach for lessons that are not yet translated

Is there anything else that should be included?

Hi,

I helped mentor a NodeSchool a few weeks ago in Reno, NV. After the workshops, the mentors got together to compare notes and we noticed that a lot of people had the same questions and problems. One of the them was the for loop exercise that already has an issue on it. A lot of students had trouble understanding "why" they would use programming and the exercises only described the "how".

We came up with the idea of re-building the exercises but incorporating a running story to help give the "why" and also attempting to clean up some of the recurring misunderstandings that we saw.

Would you be interested in seeing this as a fork of this project? Or would it be better if I created a new project?

Thanks!

At the last workshop one of the attendees got an error when starting javascripting. I tried to find the issue (which was painful due to the current structure of some modules). It seems to me that in simple-terminal-menu this line returns null:

  if (!process.stdin.isTTY)
    return null

That would mean that there's something wrong with Node though. Maybe someone else has another idea.

Writing javascript for this first time last night with this tutorial, but the tutorial's description of for loops stumped me!

I had to get my dev-friends to explain how they work. 🍕

Hey, thanks for the time you're putting into this! I'm getting a fail message on the introduction.js at the moment. I'm fairly certain I've done everything according to instruction. So, I'm stuck there, but I'm also a bit stuck on where to go to find a solution. It's indicated, "Need help? View the README for this workshop: github.com/sethvincent/javascripting" - but the README doesn't really clarify if there's a designated forum for getting help or resource for reading up on what we might be doing wrong when we receive a failure message.

for(var i = 0; i <= limit; i++)

should be

for(var i = 0; i < limit; i++)

as the task is to make 10 instead of 11 iterations.

After completing an exercise and running javascripting to select the next exercise, the workshop stays on the current exercise instead of moving to the next one I select. Repeating this process successfully moves the workshop on to the next exercise.