Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

14.0.0-14.0.2 does not work (npm/Windows) #1894

Closed
fu-sen opened this Issue Feb 16, 2019 · 16 comments

Comments

8 participants
@fu-sen
Copy link

fu-sen commented Feb 16, 2019

I upgraded now cli to 14.0.0 using npm on Windows, but now cli does not work at all:
now-cli-1400
You do not have to worry about the upgrade time. I ran this after I booted Windows.

This problem can be temporarily avoided by downgrading to 13.1.3:

 npm install -g now@13.1.3
@paulogdm

This comment has been minimized.

Copy link
Member

paulogdm commented Feb 16, 2019

@subtleGradient contributed with this:

(function (exports, require, module, __filename, __dirname) { MZ�
                                                                ^

SyntaxError: Invalid or unexpected token
    at createScript (vm.js:80:10)
    at Object.runInThisContext (vm.js:139:10)
    at Module._compile (module.js:616:28)
    at Object.Module._extensions..js (module.js:663:10)
    at Module.load (module.js:565:32)
    at tryModuleLoad (module.js:505:12)
    at Function.Module._load (module.js:497:3)
    at Function.Module.runMain (module.js:693:10)
    at startup (bootstrap_node.js:191:16)
    at bootstrap_node.js:612:3
@fu-sen

This comment has been minimized.

Copy link
Author

fu-sen commented Feb 16, 2019

I understood. I am waiting for the reflection of this renovation.
This issue will keep Open until we can see improvements.

@deebov

This comment has been minimized.

Copy link

deebov commented Feb 16, 2019

the same issue on Windows

@deebov

This comment has been minimized.

Copy link

deebov commented Feb 16, 2019

I've tried v13.1.3 but it didn't work

@lrn2prgrm

This comment has been minimized.

Copy link

lrn2prgrm commented Feb 16, 2019

Same issue here. It is severe I hope you can fix it soon

windows 10
node v10.14.2

I also got it fixed with v13.1.3. now desktop was still confused, but now-cli did the job.

@fu-sen

This comment has been minimized.

Copy link
Author

fu-sen commented Feb 17, 2019

@deebov The problem you encounter is different from this issue.
(My Now CLI worked normally until 13.1.3)

Please proceed with problem solving by either of the following:

@fu-sen

This comment has been minimized.

Copy link
Author

fu-sen commented Feb 17, 2019

@lrn2prgrm If you are using Now Desktop, you can stop automatic updating of Now CLI:
https://zeit.co/docs/v1/guides/updating-now-cli

Now Desktop and installed by npm or yarn are different Now CLI apps.
It can cause another problem:
https://github.com/zeit/now-cli/issues/1809

@paulogdm paulogdm added the bug label Feb 21, 2019

@fu-sen

This comment has been minimized.

Copy link
Author

fu-sen commented Feb 26, 2019

I confirmed the release of 14.0.1-canary.1 and tried it, but this problem is ongoing:
2019-02-26 08 59 44

It was released in 14.0.1. Therefore 14.0.1 is still a problem.

@fu-sen fu-sen changed the title 14.0.0 does not work (npm/Windows) 14.0.0-14.0.1 does not work (npm/Windows) Feb 26, 2019

@Nark0tiX

This comment has been minimized.

Copy link

Nark0tiX commented Feb 26, 2019

Indeed doesn't work here either

@fu-sen

This comment has been minimized.

Copy link
Author

fu-sen commented Feb 28, 2019

I tried 14.1.0-canary.2 but the problem is still ongoing:
2019-02-28 09 57 37

@fu-sen

This comment has been minimized.

Copy link
Author

fu-sen commented Mar 1, 2019

I tried 14.1.0-canary.3, This problem is ongoing
2019-03-01 09 32 46
:

@grantsru

This comment has been minimized.

Copy link

grantsru commented Mar 1, 2019

Still an issue for me as well. Downgrading to 13.x works in the meantime.

@fu-sen fu-sen changed the title 14.0.0-14.0.1 does not work (npm/Windows) 14.0.0-14.0.2 does not work (npm/Windows) Mar 1, 2019

@fu-sen

This comment has been minimized.

Copy link
Author

fu-sen commented Mar 1, 2019

14.0.2 has been released, but this problem is ongoing:
2019-03-01 21 45 49

@rivy

This comment has been minimized.

Copy link

rivy commented Mar 2, 2019

"now\download\dist\now" is missing/empty.
But, as a workaround, scoop can be used to install the now-win.exe directly with:

C:\>scoop install "https://raw.githubusercontent.com/rivy/scoop-bucket/master/now.json"

Additional info

When installed via yarn, the "now.cmd" file contains:

@"%~dp0\..\..\..\..\..\Yarn\Data\global\node_modules\.bin\now.cmd"   %*

That ".bin\now.cmd" file then uses node to run "%~dp0..\now\download\dist\now", but that final file is completely empty:

C:>msls -Al node_modules\now\download\dist
total 32M
-rw------a  1 Roy              572k Mar  2 12:40 index.js
-rw------a  1 Roy                 0 Mar  2 12:46 now
-rwx-----a  1 Roy               31M Mar  2 12:46 now.exe*
@AndyBitz

This comment has been minimized.

Copy link
Collaborator

AndyBitz commented Mar 3, 2019

Issue got fixed by #1922 in release 14.1.0-canary.4.

@AndyBitz AndyBitz closed this Mar 3, 2019

@fu-sen

This comment has been minimized.

Copy link
Author

fu-sen commented Mar 4, 2019

Awesome work!:
2019-03-04 09 51 27

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.