hemanth / node-nightly Goto Github PK

node-nightly --inspect --debug-brk build/build.js

C:\Users\clu\AppData\Roaming\npm\node_modules\node-nightly/node-nightly/node: [DEP0062]: node --debug and node --debug-brk are invalid. Please use node --inspect and node --inspect-brk instead.

ran into this problem with running with webpack

{ Error: EMFILE: too many open files, open '/Users/Hendrixer/.nvm/versions/node/v6.2.1/lib/node_modules/node-nightly/node-v7.0.0-nightly20160722b3127df59a-darwin-x64/lib/node_modules/npm/node_modules/iferr/index.js'
    at Error (native)
  errno: -24,
  code: 'EMFILE',
  syscall: 'open',
  path: '/Users/Hendrixer/.nvm/versions/node/v6.2.1/lib/node_modules/node-nightly/node-v7.0.0-nightly20160722b3127df59a-darwin-x64/lib/node_modules/npm/node_modules/iferr/index.js' }

Hey @hemanth! I heard that this doesn't work on Windows. What needs to happen to get this to work on Windows?

node-nightly check the latest version when executed, so it's unavailable when there is no internet connectivity. Just recently, I want to use node-nightly to run some script but there is no WIFI nearby. Is it possible to add some options like "--ignore-version" to use node-nightly when I have no network? Maybe I can do this and make a pull request.

When running node-nightly on 32-bit version, process.arch returns "ia32" which doesn't exist anywhere in node repositories neither in the files array in node-nightly-version module.

I've fixed this for myself by modifying the index.js in node-nightly.

// line 24
arch = process.arch === 'ia32' ? 'x86' : process.arch,

This fixed it for me. I'm not gonna do the pull request since this can be done better. I just wanted to inform you of this issue as other people might have the same issues.

when I first execute
node-nightly
and got
Downloading the nightly version, hang on... for almost 30mins no response

node-nightly version latest
node 14.17.0

I would find it useful to have a flag to switch between the 32/64 bit version. Currently it uses whichever is already installed.

node-nightly --arch 32 would download the same version for x86.

node-nightly --upgrade --arch 32 when upgrading, to force x86.

I could do a PR?

The installation is failing on Windows right now due to kexec because Windows uses Posix APIs!
There is an issue open for the discussion here: jprichardson/node-kexec#19

node version: 6.4.0
OS: Ubuntu 16.04
Logs:

 $node-nightly -v
/usr/lib/node_modules/node-nightly/node_modules/node-nightly-version/index.js:6
const osArch = `${process.env._system_name.toLowerCase()}-${process.arch}`;
                                          ^

TypeError: Cannot read property 'toLowerCase' of undefined

A tool for managing JavaScript projects with multiple packages
https://github.com/lerna/lerna

Not a big project, but still could be helpful to unify the small packages in a single repo..

Thoughts?

Hi,
I can't run node-nightly as it thinks I'm offline (@ home, @ work, with WiFi or wired).

~ ❯❯❯ node-nightly --upgrade
Checking for update...
You are using latest version already.
~ ❯❯❯ node-nightly
Downloading the nightly version, hang on...
 Please check your internet connectivity.
~ ❯❯❯ node -v
v6.7.0

It seems that the connectivity check is failing (sindresorhus/is-online#29 maybe) although I'm on OS X 10.11.6.

Commenting the reportIfOffline() function call fixed it for me.

~ ❯❯❯ node-nightly
Downloading the nightly version, hang on...
node-nightly is available on your CLI!
~ ❯❯❯ node-nightly
> console.log('awesome')
awesome

Please see my thread on node-sass for more details. Tldr; this package is changing the name of process.versions.node to 11.0.0-nightly20180719373aae1f86 which is making node-sass think that version 10 is being used. Is it? sass/node-sass#2460

I don't think you should do a Firefox-style upgrade prompt. "hey i know you're trying to start using firefox but do you want to interrupt what you're doing to see if you wanna upgrade." :p

The common action is people will be repeatedly running node-nightly with inspect flags, and you don't want to respond with "N" each time.

I was thinking about something that passively notified you when quitting the node process.. like..

> node-nightly --inspect index.js
Log from index.js!
^C
New nightly available. To upgrade: `node-nightly --upgrade`
> 

However, I think that'll be too noisy, even. I think it's better to leave that up to the user and just allow a --upgrade flag they can use whenever they want.

wdyt?

node-nightly --inspect --debug-brk build/build.js

Downloading the nightly version, hang on...
Error: EPERM: operation not permitted, rename 'C:\Users\clu\AppData\Roaming\npm\node_modules\node-nightly/node-v15.0.0-nightly20200518ef1eb8d439-win-x64' -> 'C:\Users\clu\AppData\Roaming\npm\node_modules\node-nightly/node-nightly'
at renameSync (fs.js:661:3)
at C:\Users\clu\AppData\Roaming\npm\node_modules\node-nightly\index.js:45:9 {
errno: -4048,
syscall: 'rename',
code: 'EPERM',
path: 'C:\Users\clu\AppData\Roaming\npm\node_modules\node-nightly/node-v15.0.0-nightly20200518ef1eb8d439-win-x64',
dest: 'C:\Users\clu\AppData\Roaming\npm\node_modules\node-nightly/node-nightly'
}

So weird..

locally i have 1.3.0

but i see https://www.npmjs.com/package/node-nightly says 1.3.1

and the repo has 1.3.2

:/

and 1.3.0 is def broken for me.

erg sorry for all the back and forth on this one.

Hey,

I want to use node-nightly at school but we have a proxy, i've already configured git and npm to use the proxy, but when i type node-nightly it says i have no internet connection

Thanks,
Mika

it repeatedly tries to download. always.

i added this

console.log(`${__dirname}/node-nightly`);

and i get this logged:

/Users/paulirish/.homebrew/lib/node_modules/node-nightly/node-nightly

I think you missed one location with dirname.. PR incoming.

looks like you're not using it any longer..

Using node-nightly I get errors like Error: Module version mismatch. Expected 51, got 48. for modules with native bindings.

I tried doing something like env NODE_PATH=/usr/local/lib/node_modules/node-nightly/node-nightly/ /usr/local/lib/node_modules/node-nightly/node-nightly/bin/npm install bcrypt but that doesn't seem to help

> npm i -g node-nightly

C:\Users\REDACTED\AppData\Roaming\npm\node-nightly -> C:\Users\REDACTED\AppData\Roaming\npm\node_modules\node-nightly\cli.js
+ [email protected]
added 160 packages in 10.488s

> node-nightly

Downloading the nightly version, hang on...
{ Error: EPERM: operation not permitted, rename 'C:\Users\tdaniely\AppData\Roaming\npm\node_modules\node-nightly\node-v10.0.0-nightly20180213e782715d0a-win-x64' -> 'C:\Users\tdaniely\AppData\Roaming\npm\node_modules\node-nightly\node-nightly'
    at fs.renameSync (fs.js:784:18)
    at download.then._ (C:\Users\tdaniely\AppData\Roaming\npm\node_modules\node-nightly\index.js:45:9)
    at <anonymous>
  errno: -4048,
  code: 'EPERM',
  syscall: 'rename',
  path: 'C:\\Users\\tdaniely\\AppData\\Roaming\\npm\\node_modules\\node-nightly\\node-v10.0.0-nightly20180213e782715d0a-win-x64',
  dest: 'C:\\Users\\tdaniely\\AppData\\Roaming\\npm\\node_modules\\node-nightly\\node-nightly' }

Should be documented.

After installing node-nightly, when I try to execute node-nightly it indicates to upgrade. But when I try to execute `node-nightly --upgrade':

node-nightly --upgrade
Checking for update...
Deleting old version
Deleted!
Installing newer version..
{ Error: EPERM: operation not permitted, rename 'C:\Users\neal1\AppData\Roaming\npm\node_modules\node-nightly\node-v8.0.0-nightly2017051384fc069b95-win-x64' -> 'C:\Users\neal1\AppData\Roaming\npm\node_modules\node-nightly\node-nightly'
    at fs.renameSync (fs.js:776:18)
    at download.then._ (C:\Users\neal1\AppData\Roaming\npm\node_modules\node-nightly\index.js:45:9)
  errno: -4048,
  code: 'EPERM',
  syscall: 'rename',
  path: 'C:\\Users\\neal1\\AppData\\Roaming\\npm\\node_modules\\node-nightly\\node-v8.0.0-nightly2017051384fc069b95-win-x64',
  dest: 'C:\\Users\\neal1\\AppData\\Roaming\\npm\\node_modules\\node-nightly\\node-nightly' }

My OS is win10 and my node version is 7.9.0. And I have tried two solutions:

1. execute npm cache clean
2. disable avast in my computer
   Unfortunately, both do not work at all.

Running node-nightly and it tries to pull down the x64 file, but it's not found in that directory.

 host: 'nodejs.org',
  hostname: 'nodejs.org',
  method: 'GET',
  path: '/download/nightly/v21.0.0-nightly202306022fca7ea2be/node-v21.0.0-nightly202306022fca7ea2be-darwin-x64.tar.gz',
  protocol: 'https:',
  url: 'https://nodejs.org/download/nightly/v21.0.0-nightly202306022fca7ea2be/node-v21.0.0-nightly202306022fca7ea2be-darwin-x64.tar.gz',
  statusCode: 404,
  statusMessage: 'Not Found',
  headers: {
    date: 'Fri, 02 Jun 2023 15:07:06 GMT',
    'content-type': 'text/html',
    'transfer-encoding': 'chunked',
    connection: 'close',
    'cache-control': 'private, no-store, max-age=0',
    'cf-cache-status': 'BYPASS',
    vary: 'Accept-Encoding',
    'strict-transport-security': 'max-age=31536000; includeSubDomains; preload',
    'x-content-type-options': 'nosniff',
    server: 'cloudflare',
    'cf-ray': '7d109aa4fc3906f4-ATL',
    'content-encoding': 'gzip'
  }

Node Version: 18.15.0
npm version: 9.5.0
OS: macOS

Nice job on this guys.

I'm working on the angular-cli and I'd like to be able to debug some of the commands we use like:
ng build
ng serve
ng build --watch --environment='subtropical'

I use node nightly like the following:
node-nightly --inspect --debug-brk ng build

However it looks like only the ng is picked up and not the secondary command. Any advice?

Development will be easier if we can inspect HTTP requests

Related to #36

I propose that --version outputs the currently used version and that something like --use would decide which version to install &/ use. This would be be more clear and follow the common --version convention for displaying version information.

Just tried node-nightly. Following is what I am getting on first time usage of the command node-nightly

{ [HTTPError: Response code 404 (Not Found)] message: 'Response code 404 (Not Found)', host: 'nodejs.org', hostname: 'nodejs.org', method: 'GET', path: '/download/nightly/v7.0.0-nightly201608085111e789e6/node-v7.0.0-nightly201608085111e789e6-darwin-x64.tar.gz', statusCode: 404, statusMessage: 'Not Found', bufferedData: <Buffer > }

What happened to the download link? Why 404? Am I missing something?

I am using Mac El Capitan.
Node - v5.2.0
NPM - 3.3.12

node-nightly --inspect --debug-brk build/build.js

Downloading the nightly version, hang on...
FetchError: request to https://nodejs.org/download/nightly/index.json failed, reason: self signed certificate in certificate chain
at ClientRequest. (C:\Users\clu\AppData\Roaming\npm\node_modules\node-nightly\node_modules\node-fetch\index.js:133:11)
at ClientRequest.emit (events.js:310:20)
at TLSSocket.socketErrorListener (_http_client.js:426:9)
at TLSSocket.emit (events.js:310:20)
at emitErrorNT (internal/streams/destroy.js:92:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:60:3)
at processTicksAndRejections (internal/process/task_queues.js:84:21) {
type: 'system',
errno: 'SELF_SIGNED_CERT_IN_CHAIN',
code: 'SELF_SIGNED_CERT_IN_CHAIN'
}

Downloading the nightly version, hang on...
{ HTTPError
    at EventEmitter.ee.on.res (/usr/local/lib/node_modules/node-nightly/node_modules/got/index.js:182:24)
    at emitOne (events.js:96:13)
    at EventEmitter.emit (events.js:189:7)
    at Immediate.setImmediate (/usr/local/lib/node_modules/node-nightly/node_modules/got/index.js:61:8)
    at runCallback (timers.js:651:20)
    at tryOnImmediate (timers.js:624:5)
    at processImmediate [as _immediateCallback] (timers.js:596:5)
  message: 'Response code 404 (Not Found)',
  host: 'nodejs.org',
  hostname: 'nodejs.org',
  method: 'GET',
  path: '/download/nightly/undefined/node-undefined-darwin-x64.tar.gz',
  statusCode: 404,
  statusMessage: 'Not Found',
  bufferedData: <Buffer > }

But after trying out:
node-nightly --upgrade

It works!

I thought it was notable that the error specifies undefined in the path.