Directory was not included into executable at compilation stage #102
Comments
Have a sort of similar issue with Error: Cannot find module './stores/memory' Stems from here, and works fine if I modify the code to just Can't seem to come up with the right blob to include the asset / scripts for this module either. Tried the following for both
Here's a quick example to reproduce: // package.json
{
"name": "pkg-cache-manager-test",
"version": "1.0.0",
"main": "index.js",
"license": "MIT",
"dependencies": {
"cache-manager": "^2.4.0"
},
"devDependencies": {
"pkg": "^3.0.5"
},
"scripts": {
"pkg": "pkg index.js"
},
"pkg": {
"scripts": [
"node_modules/cache-manager/**/*.js",
"node_modules/cache-manager/lib/stores/memory.js"
]
}
} // index.js
const cacheManager = require('cache-manager');
const memoryCache = cacheManager.caching({
store: 'memory',
}); |
Added support for |
LGTM for Still having problems with |
Hi, can you add support for "cache-manager" as well, as it seems to be still an issue. |
Hi Can you add support for "soap" as well.
|
@igorklopov "cache-manager" is still an issue here. |
Hi, I have a similar issue with node-windows. When I run .exe file I get "
". I tried adding my .js file to the .json file as "bin" and the "windw.exe" address as pkg assets. But it didn't help. the .js file under the name of "windowsServiceInstaller.js"
` `
` |
the example in this repository (https://github.com/zeit/pkg/tree/master/examples/express), when pkg to a single executable also fails,
|
Trying to work with the
oauth2orize
package. Running into some problems specifically here.Here's the full error output:
I've tried adding every combination / variation of globs I could think of which would point to the
node_modules/oauth2orize/lib/grant
directory (windows slashes, recursive from a higher folder, full paths instead of relative, including the files inside that folder directly, grabbing the entirety ofnode_modules/**/*
, etc), but I haven't found the right combination yet. Moving it out ofnode_modules
and into a locallibs
folder didn't help, either (but I didn't really expect that to work).Is my
pkg
property inpackage.json
misconfigured, or is it something else?Can reproduce by sending the following through pkg:
If I go in and re-write the
oauth2orize
code to do the following instead, it works fine (but I'd like to avoid this, if at all possible):The text was updated successfully, but these errors were encountered: