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.

Sign up for GitHub

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

Jump to bottom

Attempt to capture browser before initialized #59

Open
aliparlar opened this issue Jun 10, 2021 · 0 comments
Open

Attempt to capture browser before initialized #59

aliparlar opened this issue Jun 10, 2021 · 0 comments

Comments

@aliparlar
Copy link

I have seen
TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md
and tried working towards advised solutions (which mention node upgrade or downgrade)

Sorry for the long CONSOLE copy , please the read bottom few lines, the history is there for answering more questions.

I tried upgrading cleaning re-installing but I can't get past
TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md
/usr/local/lib/node_modules/hackium/dist/src/hackium/hackium.js:98
throw new Error('Attempt to capture browser before initialized');

The browser opens, but the bash fails.

`found 0 vulnerabilities
TKs-MacBook-Pro:Users mac$ npm install -g hackium
npm WARN deprecated [email protected]: "Please update to latest v2.3 or v2.2"
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (debug-js/debug#797)
⸨ ⸩ ⠇ reify:rxjs: timing reify:audit Completed in 994ms
⸨ ⸩ ⠇ reify:rxjs: timing reify:audit Completed in 994ms
⸨ ⸩ ⠇ reify:rxjs: timing reify:audit Completed in 994ms
⸨ ⸩ ⠇ reify:rxjs: timing reify:audit Completed in 994ms
⸨ ⸩ ⠇ reify:rxjs: timing reify:audit Completed in 994ms
⸨ ⸩ ⠇ reify:rxjs: timing reify:audit Completed in 994ms
⸨ ⸩ ⠇ reify:rxjs: timing reify:audit Completed in 994ms
⸨ ⸩ ⠇ reify:rxjs: timing reify:audit Completed in 994ms
⸨ ⸩ ⠇ reify:rxjs: timing reify:audit Completed in 994ms
⸨ ⸩ ⠇ reify:rxjs: timing reify:audit Completed in 994ms
⸨ ⸩ ⠇ reify:rxjs: timing reify:audit Completed in 994ms
⸨ ⸩ ⠇ reify:rxjs: timing reify:audit Completed in 994ms
⸨ ⸩ ⠇ reify:rxjs: timing reify:audit Completed in 994ms
⸨ ⸩ ⠇ reify:rxjs: timing reify:audit Completed in 994ms
⸨ ⸩ ⠇ reify:rxjs: timing reify:audit Completed in 994ms
⸨ ⸩ ⠇ reify:rxjs: timing reify:audit Completed in 994ms
⸨ ⸩ ⠇ reify:rxjs: timing reify:audit Completed in 994ms
⸨ ⸩ ⠇ reify:rxjs: timing reify:audit Completed in 994ms
⸨ ⸩ ⠇ reify:rxjs: timing reify:audit Completed in 994ms
⸨ ⸩ ⠇ reify:rxjs: timing reify:audit Completed in 994ms
⸨ ⸩ ⠇ reify:rxjs: timing reify:audit Completed in 994ms
⸨ ⸩ ⠇ reify:rxjs: timing reify:audit Completed in 994ms

changed 154 packages, and audited 155 packages in 2m

15 packages are looking for funding
run npm fund for details

found 0 vulnerabilities
TKs-MacBook-Pro:Users mac$
TKs-MacBook-Pro:Users mac$
TKs-MacBook-Pro:Users mac$
TKs-MacBook-Pro:Users mac$
TKs-MacBook-Pro:Users mac$
TKs-MacBook-Pro:Users mac$
TKs-MacBook-Pro:Users mac$
TKs-MacBook-Pro:Users mac$
TKs-MacBook-Pro:Users mac$
TKs-MacBook-Pro:Users mac$
TKs-MacBook-Pro:Users mac$
TKs-MacBook-Pro:Users mac$
TKs-MacBook-Pro:Users mac$
TKs-MacBook-Pro:Users mac$
TKs-MacBook-Pro:Users mac$
TKs-MacBook-Pro:Users mac$
TKs-MacBook-Pro:Users mac$
TKs-MacBook-Pro:Users mac$
TKs-MacBook-Pro:Users mac$
TKs-MacBook-Pro:Users mac$
TKs-MacBook-Pro:Users mac$
TKs-MacBook-Pro:Users mac$
TKs-MacBook-Pro:Users mac$ hackium
Info: Hackium launched

Error: Could not open history file.
REPL session history will not be persisted.

dd
Uncaught ReferenceError: dd is not defined
page.goto('https://google.com');
Promise { }
page.goto('https://greatloom.com');
Promise { }

[1]+ Stopped hackium
TKs-MacBook-Pro:Users mac$ cd hackium
-bash: cd: hackium: No such file or directory
TKs-MacBook-Pro:Users mac$ mkdir hackium
mkdir: hackium: Permission denied
TKs-MacBook-Pro:Users mac$ l
-bash: l: command not found
TKs-MacBook-Pro:Users mac$ la
-bash: la: command not found
TKs-MacBook-Pro:Users mac$ ls
Guest Shared mac
TKs-MacBook-Pro:Users mac$ cd mac
TKs-MacBook-Pro:~ mac$ mkdir hackium
mkdir: hackium: File exists
TKs-MacBook-Pro:~ mac$ cd hackium
TKs-MacBook-Pro:hackium mac$ hackium
Error: Hackium failed during bootup and may be in an unstable state.
Error: Error: Failed to launch the browser process!

TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md

(node:14679) UnhandledPromiseRejectionWarning: Error: Attempt to capture browser before initialized
at Hackium.getBrowser (/usr/local/lib/node_modules/hackium/dist/src/hackium/hackium.js:98:19)
at /usr/local/lib/node_modules/hackium/dist/src/cli.js:85:39
at processTicksAndRejections (internal/process/task_queues.js:95:5)
(Use node --trace-warnings ... to show where the warning was created)
(node:14679) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
(node:14679) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
TKs-MacBook-Pro:hackium mac$
TKs-MacBook-Pro:hackium mac$
TKs-MacBook-Pro:hackium mac$ hackium init
Initializing config
? What URL do you want to load by default? google.com
? Do you want to open devtools automatically? Yes
? Do you want to create a blank JavaScript injection? Yes
? Do you want to add a boilerplate interceptor? Yes
? Do you want to add a boilerplate Hackium script? Yes
? Do you want to run headless? No
Writing to ./hackium.config.js
TKs-MacBook-Pro:hackium mac$ ls
hackium.config.js interceptor.js script.js
inject.js package.json
TKs-MacBook-Pro:hackium mac$ hackium -e script.js
Info: using config found at '/Users/mac/hackium/hackium.config.js'
Error: Hackium failed during bootup and may be in an unstable state.
Error: Error: Failed to launch the browser process!

TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md

(node:14700) UnhandledPromiseRejectionWarning: Error: Attempt to capture browser before initialized
at Hackium.getBrowser (/usr/local/lib/node_modules/hackium/dist/src/hackium/hackium.js:98:19)
at /usr/local/lib/node_modules/hackium/dist/src/cli.js:85:39
at processTicksAndRejections (internal/process/task_queues.js:95:5)
(Use node --trace-warnings ... to show where the warning was created)
(node:14700) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
(node:14700) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
TKs-MacBook-Pro:hackium mac$ hackium -e script.js
Info: using config found at '/Users/mac/hackium/hackium.config.js'
Error: Hackium failed during bootup and may be in an unstable state.
Error: Error: Failed to launch the browser process!

TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md

(node:14714) UnhandledPromiseRejectionWarning: Error: Attempt to capture browser before initialized
at Hackium.getBrowser (/usr/local/lib/node_modules/hackium/dist/src/hackium/hackium.js:98:19)
at /usr/local/lib/node_modules/hackium/dist/src/cli.js:85:39
at processTicksAndRejections (internal/process/task_queues.js:95:5)
(Use node --trace-warnings ... to show where the warning was created)
(node:14714) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
(node:14714) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
TKs-MacBook-Pro:hackium mac$ hackium -e script.js -d
Info: using config found at '/Users/mac/hackium/hackium.config.js'
Error: Hackium failed during bootup and may be in an unstable state.
Error: Error: Failed to launch the browser process!

TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md

(node:14767) UnhandledPromiseRejectionWarning: Error: Attempt to capture browser before initialized
at Hackium.getBrowser (/usr/local/lib/node_modules/hackium/dist/src/hackium/hackium.js:98:19)
at /usr/local/lib/node_modules/hackium/dist/src/cli.js:85:39
at processTicksAndRejections (internal/process/task_queues.js:95:5)
(Use node --trace-warnings ... to show where the warning was created)
(node:14767) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
(node:14767) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
TKs-MacBook-Pro:hackium mac$ hackium -e script.js -d
Info: using config found at '/Users/mac/hackium/hackium.config.js'
Error: Hackium failed during bootup and may be in an unstable state.
Error: Error: Failed to launch the browser process!

TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md

(node:14781) UnhandledPromiseRejectionWarning: Error: Attempt to capture browser before initialized
at Hackium.getBrowser (/usr/local/lib/node_modules/hackium/dist/src/hackium/hackium.js:98:19)
at /usr/local/lib/node_modules/hackium/dist/src/cli.js:85:39
at processTicksAndRejections (internal/process/task_queues.js:95:5)
(Use node --trace-warnings ... to show where the warning was created)
(node:14781) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
(node:14781) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
TKs-MacBook-Pro:hackium mac$ npm uninstall -g hackium

removed 154 packages, and audited 1 package in 1s

found 0 vulnerabilities
TKs-MacBook-Pro:hackium mac$ npm install -g hackium
npm WARN deprecated [email protected]: "Please update to latest v2.3 or v2.2"
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (debug-js/debug#797)

added 154 packages, and audited 155 packages in 2m

15 packages are looking for funding
run npm fund for details

found 0 vulnerabilities
TKs-MacBook-Pro:hackium mac$ npm install -g hackium
npm WARN deprecated [email protected]: "Please update to latest v2.3 or v2.2"
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (debug-js/debug#797)

changed 154 packages, and audited 155 packages in 2m

15 packages are looking for funding
run npm fund for details

found 0 vulnerabilities
TKs-MacBook-Pro:hackium mac$ hackium -e script.js -d
Info: using config found at '/Users/mac/hackium/hackium.config.js'
Error: Hackium failed during bootup and may be in an unstable state.
Error: Error: Failed to launch the browser process!

TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md

(node:14843) UnhandledPromiseRejectionWarning: Error: Attempt to capture browser before initialized
at Hackium.getBrowser (/usr/local/lib/node_modules/hackium/dist/src/hackium/hackium.js:98:19)
at /usr/local/lib/node_modules/hackium/dist/src/cli.js:85:39
at processTicksAndRejections (internal/process/task_queues.js:95:5)
(Use node --trace-warnings ... to show where the warning was created)
(node:14843) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
(node:14843) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
TKs-MacBook-Pro:hackium mac$ hackium
Info: using config found at '/Users/mac/hackium/hackium.config.js'
Error: Hackium failed during bootup and may be in an unstable state.
Error: Error: Failed to launch the browser process!

TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md

(node:14887) UnhandledPromiseRejectionWarning: Error: Attempt to capture browser before initialized
at Hackium.getBrowser (/usr/local/lib/node_modules/hackium/dist/src/hackium/hackium.js:98:19)
at /usr/local/lib/node_modules/hackium/dist/src/cli.js:85:39
at processTicksAndRejections (internal/process/task_queues.js:95:5)
(Use node --trace-warnings ... to show where the warning was created)
(node:14887) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
(node:14887) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
TKs-MacBook-Pro:hackium mac$ page.goto('https://ppce-clients.s3.amazonaws.com/Html/index.html');
-bash: syntax error near unexpected token 'https://ppce-clients.s3.amazonaws.com/Html/index.html'' TKs-MacBook-Pro:hackium mac$ page.goto('https://ppce-clients.s3.amazonaws.com/Html/index.html'); -bash: syntax error near unexpected token 'https://ppce-clients.s3.amazonaws.com/Html/index.html''
TKs-MacBook-Pro:hackium mac$ hackium
Info: using config found at '/Users/mac/hackium/hackium.config.js'
Error: Hackium failed during bootup and may be in an unstable state.
Error: Error: Failed to launch the browser process!

TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md

(node:14919) UnhandledPromiseRejectionWarning: Error: Attempt to capture browser before initialized
at Hackium.getBrowser (/usr/local/lib/node_modules/hackium/dist/src/hackium/hackium.js:98:19)
at /usr/local/lib/node_modules/hackium/dist/src/cli.js:85:39
at processTicksAndRejections (internal/process/task_queues.js:95:5)
(Use node --trace-warnings ... to show where the warning was created)
(node:14919) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
(node:14919) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
TKs-MacBook-Pro:hackium mac$ npm -v
7.16.0
TKs-MacBook-Pro:hackium mac$ node -v
v14.17.0
TKs-MacBook-Pro:hackium mac$ npm update node -g

removed 3590 packages, and audited 1 package in 13s

found 0 vulnerabilities
TKs-MacBook-Pro:hackium mac$ node -v
v16.3.0
TKs-MacBook-Pro:hackium mac$ npm -v
7.15.1
TKs-MacBook-Pro:hackium mac$ npm uninstall -g hackium

up to date, audited 1 package in 263ms

found 0 vulnerabilities
TKs-MacBook-Pro:hackium mac$ npm install -g hackium
npm WARN deprecated [email protected]: "Please update to latest v2.3 or v2.2"
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (debug-js/debug#797)

added 154 packages, and audited 155 packages in 2m

15 packages are looking for funding
run npm fund for details

found 0 vulnerabilities
TKs-MacBook-Pro:hackium mac$ npm install fsevents

added 1 package, and audited 2 packages in 895ms

found 0 vulnerabilities
TKs-MacBook-Pro:hackium mac$ npm install debug

added 2 packages, and audited 4 packages in 1s

found 0 vulnerabilities
TKs-MacBook-Pro:hackium mac$ hackium
Info: using config found at '/Users/mac/hackium/hackium.config.js'
Error: Hackium failed during bootup and may be in an unstable state.
Error: Error: Failed to launch the browser process!

TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md

/usr/local/lib/node_modules/hackium/dist/src/hackium/hackium.js:98
throw new Error('Attempt to capture browser before initialized');
^

Error: Attempt to capture browser before initialized
at Hackium.getBrowser (/usr/local/lib/node_modules/hackium/dist/src/hackium/hackium.js:98:19)
at /usr/local/lib/node_modules/hackium/dist/src/cli.js:85:39
at processTicksAndRejections (node:internal/process/task_queues:96:5)
TKs-MacBook-Pro:hackium mac$
TKs-MacBook-Pro:hackium mac$ sudo hackium
Password:
Error: error importing configuration:
Error: Cannot find module 'hackium.config.js'
Require stack:

  • /usr/local/lib/node_modules/hackium/dist/src/cli.js
  • /usr/local/lib/node_modules/hackium/bin/hackium
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:941:15)
    at Function.Module._load (node:internal/modules/cjs/loader:774:27)
    at Module.require (node:internal/modules/cjs/loader:1013:19)
    at require (node:internal/modules/cjs/helpers:93:18)
    at _runCli (/usr/local/lib/node_modules/hackium/dist/src/cli.js:56:36) {
    code: 'MODULE_NOT_FOUND',
    requireStack: [
    '/usr/local/lib/node_modules/hackium/dist/src/cli.js',
    '/usr/local/lib/node_modules/hackium/bin/hackium'
    ]
    }
    Error: Hackium failed during bootup and may be in an unstable state.
    Error: Error: Failed to launch the browser process!

TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md

/usr/local/lib/node_modules/hackium/dist/src/hackium/hackium.js:98
throw new Error('Attempt to capture browser before initialized');
^

Error: Attempt to capture browser before initialized
at Hackium.getBrowser (/usr/local/lib/node_modules/hackium/dist/src/hackium/hackium.js:98:19)
at /usr/local/lib/node_modules/hackium/dist/src/cli.js:85:39
at processTicksAndRejections (node:internal/process/task_queues:96:5)
TKs-MacBook-Pro:hackium mac$ npm -v
7.15.1
TKs-MacBook-Pro:hackium mac$ node -v
v16.3.0
TKs-MacBook-Pro:hackium mac$ cd hackium
-bash: cd: hackium: No such file or directory
TKs-MacBook-Pro:hackium mac$ ls
hackium.config.js inject.js interceptor.js node_modules package-lock.json package.json script.js zorba-bash
TKs-MacBook-Pro:hackium mac$ hackium
Info: using config found at '/Users/mac/hackium/hackium.config.js'
Error: Hackium failed during bootup and may be in an unstable state.
Error: Error: Failed to launch the browser process!

TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md

/usr/local/lib/node_modules/hackium/dist/src/hackium/hackium.js:98
throw new Error('Attempt to capture browser before initialized');
^

Error: Attempt to capture browser before initialized
at Hackium.getBrowser (/usr/local/lib/node_modules/hackium/dist/src/hackium/hackium.js:98:19)
at /usr/local/lib/node_modules/hackium/dist/src/cli.js:85:39
at processTicksAndRejections (node:internal/process/task_queues:96:5)
TKs-MacBook-Pro:hackium mac$ cd ..
TKs-MacBook-Pro:~ mac$ hackium
Error: Hackium failed during bootup and may be in an unstable state.
Error: Error: Failed to launch the browser process!

TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md

/usr/local/lib/node_modules/hackium/dist/src/hackium/hackium.js:98
throw new Error('Attempt to capture browser before initialized');
^

Error: Attempt to capture browser before initialized
at Hackium.getBrowser (/usr/local/lib/node_modules/hackium/dist/src/hackium/hackium.js:98:19)
at /usr/local/lib/node_modules/hackium/dist/src/cli.js:85:39
at processTicksAndRejections (node:internal/process/task_queues:96:5)
TKs-MacBook-Pro:~ mac$ node -v
v16.3.0
TKs-MacBook-Pro:~ mac$ cd hackium
TKs-MacBook-Pro:hackium mac$ ls
hackium.config.js inject.js interceptor.js node_modules package-lock.json package.json script.js zorba-bash
TKs-MacBook-Pro:hackium mac$ npm install

added 3 packages, and audited 4 packages in 971ms

found 0 vulnerabilities
TKs-MacBook-Pro:hackium mac$ hackium
Info: using config found at '/Users/mac/hackium/hackium.config.js'
Error: Hackium failed during bootup and may be in an unstable state.
Error: Error: Failed to launch the browser process!

TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md

/usr/local/lib/node_modules/hackium/dist/src/hackium/hackium.js:98
throw new Error('Attempt to capture browser before initialized');
^

Error: Attempt to capture browser before initialized
at Hackium.getBrowser (/usr/local/lib/node_modules/hackium/dist/src/hackium/hackium.js:98:19)
at /usr/local/lib/node_modules/hackium/dist/src/cli.js:85:39
at processTicksAndRejections (node:internal/process/task_queues:96:5)
TKs-MacBook-Pro:hackium mac$ hackium init
Initializing config
? What URL do you want to load by default? https://google.com
? Do you want to open devtools automatically? No
? Do you want to create a blank JavaScript injection? No
? Do you want to add a boilerplate interceptor? No
? Do you want to add a boilerplate Hackium script? No
? Do you want to run headless? No
Writing to ./hackium.config.js
TKs-MacBook-Pro:hackium mac$ hackium
Info: using config found at '/Users/mac/hackium/hackium.config.js'
Error: Hackium failed during bootup and may be in an unstable state.
Error: Error: Failed to launch the browser process!

TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md

/usr/local/lib/node_modules/hackium/dist/src/hackium/hackium.js:98
throw new Error('Attempt to capture browser before initialized');
^

Error: Attempt to capture browser before initialized
at Hackium.getBrowser (/usr/local/lib/node_modules/hackium/dist/src/hackium/hackium.js:98:19)
at /usr/local/lib/node_modules/hackium/dist/src/cli.js:85:39
at processTicksAndRejections (node:internal/process/task_queues:96:5)
TKs-MacBook-Pro:hackium mac$ npm uninstall -g hackium

removed 154 packages, and audited 1 package in 1s

found 0 vulnerabilities
TKs-MacBook-Pro:hackium mac$ sudo npm install -g hackium
Password:
npm WARN deprecated [email protected]: "Please update to latest v2.3 or v2.2"
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (debug-js/debug#797)

added 154 packages, and audited 155 packages in 2m

15 packages are looking for funding
run npm fund for details

found 0 vulnerabilities
TKs-MacBook-Pro:hackium mac$ hackium
Info: using config found at '/Users/mac/hackium/hackium.config.js'
Error: Hackium failed during bootup and may be in an unstable state.
Error: Error: Failed to launch the browser process!

TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md

/usr/local/lib/node_modules/hackium/dist/src/hackium/hackium.js:98
throw new Error('Attempt to capture browser before initialized');
^

Error: Attempt to capture browser before initialized
at Hackium.getBrowser (/usr/local/lib/node_modules/hackium/dist/src/hackium/hackium.js:98:19)
at /usr/local/lib/node_modules/hackium/dist/src/cli.js:85:39
at processTicksAndRejections (node:internal/process/task_queues:96:5)
TKs-MacBook-Pro:hackium mac$ node -v
v16.3.0
TKs-MacBook-Pro:hackium mac$ npm -v
`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@aliparlar