it doesn't connect to daemon without passing tls and macaroon strings about ln-service

[alexbosworth]

This was exposed in index

[alexbosworth]

The credentials were split up so there is a new env variable needed to specify which chain you are using

https://github.com/alexbosworth/ln-service#configuring-environment-variables

[grunch]

I know, I have configured that credentials, the issue is not allowed to use just indicate the path of my tls.cert, now is forced to enter the base64 string, previous versions let you do it in the two ways

[alexbosworth]

You can try service/local_lnd.js to retrieve the local LND via the path

[grunch]

I did, I told you in the first post, did you read it?

[grunch]

Maybe I didn't explained myself well, I added service/local_lnd.js to the main index.js, then imported to connect through it, but I get that promisify error I wrote up there

[alexbosworth]

I don't know what the code looks like but it seems like the require isn't specified correctly then, try the full relative path to the file and no destructuring

[grunch]

same thing

[alexbosworth]

I think it's because you're using promisify but this is not a callback function

[plwalters]

Can you paste your code here?

[grunch]

#./index.js
....
const {updateRoutingFees} = require('./lightning');
const {verifyMessage} = require('./lightning');
const {localLnd} = require('./service'); <== added line

module.exports = {
  localLnd, <== added line
  addPeer,
  closeChannel,
.....

# my connect.js
const { localLnd } = require('ln-service');

const lnd = localLnd({});

I had all LND_GRPC_PORT, LND_HOST, LNSERVICE_LND_DIR, LNSERVICE_CHAIN, LNSERVICE_NETWORK vars setted.

[alexbosworth]

I tried exposing it now in index.js

[grunch]

@alexbosworth why this was closed?