vercel/hyper

HyperCLI and WSL

Open

#3,432 opened on Jan 23, 2019

View on GitHub
 (2 comments) (2 reactions) (0 assignees)TypeScript (44,582 stars) (3,558 forks)batch import
help wanted🎨 Type: Enhancement🖼 Platform: Windows

Description

As a follow up to https://github.com/zeit/hyper/pull/2375

This https://github.com/zeit/hyper/blob/master/build/win/hyper#L8 can probably be fixed now by using WSLENV https://blogs.msdn.microsoft.com/commandline/2017/12/22/share-environment-vars-between-wsl-and-windows/

Contributor guide

Tech stack
shellnodejs
Domain
devopstooling
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Windows Subsystem for Linux (WSL)shell scriptingHyper build process
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Examine the referenced file 'build/win/hyper' and the previous PR #2375. Understand how WSLENV can be used to share environment variables between WSL and Windows. Implement the change to set WSLENV appropriately, and test by running Hyper on WSL. If needed, ask maintainers about any additional considerations.