vercel / vercel/hyper

Nextjs build errors that don't appear in other command line clients

Open
#4,607 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
44.7k
Forks
3.6k
Avg merge
21m
Merged PRs (30d)
1

Description

  • [ X] I am on the latest Hyper.app version
  • [ X] I have searched the issues of this repo and believe that this is not a duplicate
  • OS version and name: windows 10
  • Hyper.app version: 3.02
  • Link of a Gist with the contents of your .hyper.js:
  • Relevant information from devtools (CMD+ALT+I on macOS, CTRL+SHIFT+I elsewhere):
  • The issue is reproducible in vanilla Hyper.app: idk yet how to restore to vanilla state after installing some plugins?

Issue

npm run build suddenly gives me build errors that I cannot replicate in other command line clients (gitbash, powershell, vscode terminal...)
Annotation 2020-06-02 175214

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Start by reproducing npm run build in Hyper.app 3.02 on Windows 10 and compare the result with Git Bash, PowerShell, and the VS Code terminal. Check whether the behavior persists in vanilla Hyper.app; done means identifying a reproducible Hyper-specific cause and documenting or fixing the differing build errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, nextjs
Domain
cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.