Issues: vercel/pkg
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
copyFolderRecursiveSync exits early while copying files from node_modules
#1967
opened Jul 21, 2023 by
jackkav
Cannot use external c-bindings within pkg exe, causes immediate failure when trying to load package.
#1966
opened Jul 19, 2023 by
EzzypooOfNazareth
"Error: Cannot find module" for a module that definitely exists
#1962
opened Jul 17, 2023 by
iameli-streams
Solution to #1657 Warning Cannot include file %1 into executable
#1961
opened Jul 16, 2023 by
good1uck
Files packaged with code containing pupeteer-core 20.4.0 or higher cannot be executed
#1947
opened Jun 16, 2023 by
MCHK0306
link-module-alias for Nodejs Javascript project (not Typescript)
#1946
opened Jun 16, 2023 by
joshuaquek
Better error message than "AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value"
#1938
opened May 22, 2023 by
samuelko123
how to run linux compiled node.js script in linux? i dont know the commands
#1935
opened May 19, 2023 by
TERRYKOLBEN
pkg@5.8.1 "No available node version satisfies node16.14.2"
#1932
opened May 15, 2023 by
SpacewormSera
Reading the root of a drive on windows results extra 'snapshot' directory
#1929
opened May 11, 2023 by
vicapow
Is it possible to use a specific node version (16.8) in Vercel?
#1927
opened May 11, 2023 by
SpacewormSera
Not working with sharp again "Cannot include directory %1 into executable."
#1918
opened Apr 20, 2023 by
rightaway
Impossible to link to own shared library from native node module
#1911
opened Apr 15, 2023 by
Zubnix
Previous Next
ProTip!
Find all open issues with in progress development work with linked:pr.