-
-
Notifications
You must be signed in to change notification settings - Fork 523
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
[v6] webpack: keytar native module has hardcoded path #1029
Comments
In order to debug your problem further, we need a minimal testcase to reproduce your problem. Using |
Sure, will do, I'll try to provide you with that in the next few days.
…On Mon., Jul. 15, 2019, 8:11 p.m. Mark Lee, ***@***.***> wrote:
In order to debug your problem further, we need a minimal testcase to
reproduce your problem. Using create-electron-app --template=webpack as a
base, could you please create a minimal Electron app that illustrates the
issue you described, and post a link to it here?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1029>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AC6LESVA4PRHHZCLDZ5N7LDP7UG3TANCNFSM4IDTT4VA>
.
|
With the details currently provided, I cannot reproduce the behavior by simply adding the |
I'll try to reproduce the issue with a minimum reproducible case, maybe
it's only related to keytar specifically, I'll try to look into it asap
…On Mon., Jul. 15, 2019, 8:21 p.m. Mark Lee, ***@***.***> wrote:
With the details currently provided, I cannot reproduce the behavior by
simply adding the ref native module to a Forge v6 project using Webpack.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1029>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AC6LESQOENRGND7UCUO4S4DP7UIBDANCNFSM4IDTT4VA>
.
|
Here's a MRC. What I did:
After noticing the issue with the prepare native dep on the make step, I tested this:
I noticed that It seems odd to me that keytar is the only native node module impacted, I'll try to reproduce with another |
@MarshallOfSound does this have something to do with https://github.com/marshallofsound/webpack-asset-relocator-loader ? |
+1 Seems webpack-asset-relocator-loader we are using does not handle it correctly. |
Did anyone figure this out? I'm having a similar issue with |
+1 The same error as described above OS: Windows |
Got it work
There was module |
Thanks @shezuka-monkey!! That fixed it for me: Before module.exports = [
// Add support for native node modules
{
test: /\.node$/,
use: 'node-loader',
},
{
test: /\.(m?js|node)$/,
parser: { amd: false },
use: {
loader: '@marshallofsound/webpack-asset-relocator-loader',
options: {
outputAssetBase: 'native_modules',
},
},
},
]; After module.exports = [
// Add support for native node modules
{
test: /\.(m?js|node)$/,
parser: { amd: false },
use: {
loader: '@marshallofsound/webpack-asset-relocator-loader',
options: {
outputAssetBase: 'native_modules',
},
},
},
]; |
keytar works fine for me with the webpack template, Electron Forge v6 beta 61 and keytar 7.7.0 on Linux (which uses Node-API and prebuild-install).
Add to the top of const keytar = require('keytar');
keytar.findPassword('nonexistentservice').then(result => console.log('KEYTAR RESULT', result)); Then run |
Bumps [actions/setup-node](https://github.com/actions/setup-node) from 2.5.1 to 3.1.0. - [Release notes](https://github.com/actions/setup-node/releases) - [Commits](actions/setup-node@v2.5.1...v3.1.0) --- updated-dependencies: - dependency-name: actions/setup-node dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Using the default webpack template, my node native are loaded somewhat like this, using absolute path:
Obviously, it works fine till I blast my node_module folder to oblivion, but as soon as I do, or -more importantly- try to distribute my app, it doesn't work.
The text was updated successfully, but these errors were encountered: