Suggestion: Assist new Windows developers by mentioning win-node-env in README #235

New issue

Closed

opened 2019-01-25 19:32:48 +01:00 by Wick · 2 comments

Wick commented

2019-01-25 19:32:48 +01:00

(Migrated from github.com)

You might want to mention somewhere that Windows developers need something like win-node-env (https://github.com/laggingreflex/win-node-env) to be able to run npm run start without getting error on NODE_ENV=production

Reference: https://stackoverflow.com/questions/11928013/node-env-is-not-recognized-as-an-internal-or-external-command-operable-comman

You might want to mention somewhere that Windows developers need something like ```win-node-env``` (https://github.com/laggingreflex/win-node-env) to be able to run ```npm run start``` without getting error on ```NODE_ENV=production``` Reference: https://stackoverflow.com/questions/11928013/node-env-is-not-recognized-as-an-internal-or-external-command-operable-comman

kauffj commented

2019-01-25 22:30:36 +01:00

(Migrated from github.com)

@Wick would you be able or willing to update the README and/or dependencies so that this works? I don't believe anyone at our company actively develops on Windows. Happy to send some LBC as appreciation.

Wick commented

2019-01-26 14:13:07 +01:00

(Migrated from github.com)

Yeah, I'll take a look. :)

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

LBRYCommunity/lbry.tech#235

No description provided.

Rows
Columns