Skip to content
This repository has been archived by the owner on Jan 13, 2024. It is now read-only.

Help with packaging a project #989

Closed
billtlee opened this issue Oct 24, 2020 · 5 comments
Closed

Help with packaging a project #989

billtlee opened this issue Oct 24, 2020 · 5 comments
Labels

Comments

@billtlee
Copy link

Hi,

I am playing with pkg and when I try to run the executable, I got an error saying one of the required components is not available. Can someone please let me know what I might be doing wrong?

Here is the link to the git repository:

https://github.com/billtlee/ginit

Thanks in advance!

@lselden
Copy link

lselden commented Nov 3, 2020

My guess is that one of your dependencies includes a native addon - pkg will warn about that. Otherwise it may be that pkg couldn't detect some source files - check the README about how to include. Otherwise you might get more help if you include the actual error message.

@billtlee
Copy link
Author

billtlee commented Dec 9, 2020

@lselden
Thanks for getting back! The pkg command actually works and does create the executables. However when I run the executable on my mac for example, I am getting the following error:

pkg/prelude/bootstrap.js:1244
throw error;
^

Error [ERR_INSPECTOR_NOT_AVAILABLE]: Inspector is not available
at inspector.js:24:9
at NativeModule.compileForInternalLoader (internal/bootstrap/loaders.js:276:7)
at NativeModule.compileForPublicLoader (internal/bootstrap/loaders.js:218:10)
at loadNativeModule (internal/modules/cjs/helpers.js:25:9)
at Function.Module._load (internal/modules/cjs/loader.js:906:15)
at Module.require (internal/modules/cjs/loader.js:1087:19)
at Module.require (pkg/prelude/bootstrap.js:1225:31)
at require (internal/modules/cjs/helpers.js:73:18)
at Object. (/snapshot/ginit/lib/repo.js:11:17)
at Module._compile (pkg/prelude/bootstrap.js:1320:22) {
code: 'ERR_INSPECTOR_NOT_AVAILABLE'
}

@lselden
Copy link

lselden commented Dec 10, 2020

Looks like you're trying to use --inspect, or a package you're using is trying to use the inspector, which is disabled by pkg. See #93

@github-actions
Copy link

This issue is stale because it has been open 90 days with no activity. Remove the stale label or comment or this will be closed in 5 days. To ignore this issue entirely you can add the no-stale label

@github-actions github-actions bot added the Stale label Mar 25, 2021
@github-actions
Copy link

This issue is now closed due to inactivity, you can of course reopen or reference this issue if you see fit.

jesec added a commit to vercel/pkg-fetch that referenced this issue May 1, 2022
Production binaries shall NOT take NODE_OPTIONS from end-users.

Only the users (developers who use pkg to package their project) should
have control over the flags via the "bake in" (--options) mechanism.

Bug: vercel/pkg#954, vercel/pkg#989, vercel/pkg#1194, vercel/pkg#1517
jesec added a commit to jesec/pkg-fetch that referenced this issue May 3, 2022
Production binaries shall NOT take NODE_OPTIONS from end-users.

Only the users (developers who use pkg to package their project) should
have control over the flags via the "bake in" (--options) mechanism.

Bug: vercel/pkg#954, vercel/pkg#989, vercel/pkg#1194, vercel/pkg#1517
Hypfer pushed a commit to Hypfer/pkg-fetch that referenced this issue May 7, 2022
Production binaries shall NOT take NODE_OPTIONS from end-users.

Only the users (developers who use pkg to package their project) should
have control over the flags via the "bake in" (--options) mechanism.

Bug: vercel/pkg#954, vercel/pkg#989, vercel/pkg#1194, vercel/pkg#1517
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants