Core/Javascripting/1.Introduction

Open
#215 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript, node.js, powershell
Domain
cli, operating-systems, tooling

Research direction

Start by reproducing the Core/Javascripting/1.Introduction verification flow on Windows 10 in PowerShell, using an empty file created with $null > file.extension or an editor, then compare it with the Command Prompt case. Trace the javascripting verify entry point to identify why the empty file is rejected. Done means valid empty files work across the reported creation methods, or the guide clearly documents the supported Windows procedure.

Written by the indexing model from the issue text.

Description

help wanted translation

On Windows 10, in PowerShell, you cannot create an empty file using the type NUL > file.extension command.
The only way for the javascripting verifiy command to ever be successful is to create an empty file using the type NUL > file.extension command from CommandPrompt only. This isn't mentioned anywhere in the guide (it just says on Windows).
Even if you create an empty file with $null > file.extension, the validation fails and you can't even run it with node file.extension. The same applies when you create the file in a text editor or in an IDE.

  • node version: v9.3.0
  • npm version: 5.6.0
  • os: Microsoft Windows [Version 10.0.16299.125]
Error output when trying to verify a file that was not created in CommandPrompt using the type NUL > file.extension command.
SyntaxError: Invalid or unexpected token
    at createScript (vm.js:80:10)
    at Object.runInThisContext (vm.js:152:10)
    at Module._compile (module.js:624:28)
    at Object.Module._extensions..js (module.js:671:10)
    at Module.load (module.js:573:32)
    at tryModuleLoad (module.js:513:12)
    at Function.Module._load (module.js:505:3)
    at Function.Module.runMain (module.js:701:10)
    at startup (bootstrap_node.js:194:16)
    at bootstrap_node.js:618:3

    at ChildProcess.exithandler (child_process.js:272:12)
    at ChildProcess.emit (events.js:159:13)
    at maybeClose (internal/child_process.js:943:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:220:5)
  killed: false,
  code: 1,
  signal: null,
My Code
 console.log('hello');
Dominant language
JavaScript
Stars
2.9k
Forks
1k
Avg merge
14h 47m
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from workshopper/javascripting

All issues in workshopper/javascripting

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.