stebalien changed the topic of #ipfs to: Heads Up: To talk, you need to register your nick! Announcements: go-ipfs 0.5.1 and js-ipfs 0.43.1 are out! Get them from dist.ipfs.io and npm respectively! | Also: #libp2p #ipfs-cluster #filecoin #ipfs-dev | IPFS: https://github.com/ipfs/ipfs | Logs: https://view.matrix.org/room/!yhqiEdqNjyPbxtUjzm:matrix.org/ | Forums: https://discuss.ipfs.io | Code of Conduct: https://git.io/vVBS0
Pie-jacker875 has quit [Read error: Connection reset by peer]
Pie-jacker875 has joined #ipfs
lawr3nce has joined #ipfs
Trieste has quit [Ping timeout: 260 seconds]
lawr3nce has quit [Remote host closed the connection]
Trieste has joined #ipfs
}ls{ has quit [Ping timeout: 264 seconds]
}ls{ has joined #ipfs
stoopkid has quit [Quit: Connection closed for inactivity]
Ecran has quit [Quit: Going offline, see ya! (www.adiirc.com)]
stoopkid has joined #ipfs
nbonfils[m] has joined #ipfs
Relis has quit [Quit: This computer has gone to sleep]
endvra has quit [Read error: Connection reset by peer]
endvra has joined #ipfs
cry0 has joined #ipfs
cramte[m] has joined #ipfs
jadedctrl has joined #ipfs
Relis has joined #ipfs
xcm has quit [Remote host closed the connection]
xcm has joined #ipfs
AbramAdelmo has joined #ipfs
AbramAdelmo has quit [Ping timeout: 260 seconds]
cry0 has quit [Ping timeout: 272 seconds]
Belkaar has quit [Ping timeout: 260 seconds]
Belkaar has joined #ipfs
Belkaar has joined #ipfs
Belkaar has quit [Changing host]
cry0 has joined #ipfs
Relis has quit [Quit: This computer has gone to sleep]
jadedctrl has quit [Quit: Vision[0.10.3]: i've been blurred!]
jadedctrl has joined #ipfs
Jeanne-Kamikaze has joined #ipfs
GuerrillaMonkey has quit [Ping timeout: 260 seconds]
jcea has quit [Quit: jcea]
cry0 has quit [Ping timeout: 260 seconds]
jrt has quit [Killed (verne.freenode.net (Nickname regained by services))]
jrt has joined #ipfs
Relis has joined #ipfs
fling has joined #ipfs
mowotter has quit [Remote host closed the connection]
fling has quit [Ping timeout: 260 seconds]
Relis has quit [Quit: This computer has gone to sleep]
KempfCreative has joined #ipfs
user_51 has quit [Ping timeout: 246 seconds]
user_51 has joined #ipfs
cris_thor` has left #ipfs [#ipfs]
cris has joined #ipfs
Acacia has quit [Ping timeout: 260 seconds]
cris has quit []
cris has joined #ipfs
Trieste has quit [Ping timeout: 240 seconds]
Acacia has joined #ipfs
Trieste has joined #ipfs
KempfCreative has quit [Ping timeout: 272 seconds]
KindTwo has joined #ipfs
KindOne has quit [Ping timeout: 272 seconds]
KindTwo is now known as KindOne
KindTwo has joined #ipfs
KindOne has quit [Ping timeout: 246 seconds]
KindTwo is now known as KindOne
RingtailedFox has quit [Read error: Connection reset by peer]
KindTwo has joined #ipfs
KindOne has quit [Ping timeout: 272 seconds]
KindTwo is now known as KindOne
AbramAdelmo has joined #ipfs
AbramAdelmo has quit [Ping timeout: 264 seconds]
AbramAdelmo has joined #ipfs
AbramAdelmo has quit [Ping timeout: 246 seconds]
ecs has quit [Excess Flood]
ecs has joined #ipfs
joocain2 has quit [Remote host closed the connection]
lnostdal has quit [Remote host closed the connection]
AbramAdelmo has joined #ipfs
AbramAdelmo has quit [Ping timeout: 264 seconds]
dannycarrera3 has joined #ipfs
dannycarrera3 has quit [Remote host closed the connection]
dannycarrera has joined #ipfs
<dannycarrera>
Hello!
bengates has quit [Remote host closed the connection]
<dannycarrera>
Could someone point me in the direction of how to enable step through debugging with ipfs-companion?
AbramAdelmo has joined #ipfs
AbramAdelmo has quit [Ping timeout: 264 seconds]
Acacia has quit [Ping timeout: 272 seconds]
Acacia has joined #ipfs
AbramAdelmo has joined #ipfs
Telior has quit [Ping timeout: 245 seconds]
AbramAdelmo has quit [Ping timeout: 240 seconds]
xcm has quit [Remote host closed the connection]
xcm has joined #ipfs
mowcat has quit [Remote host closed the connection]
DowwieDiscord[m] has left #ipfs ["User left"]
<dannycarrera>
Hello, anyone active?
<lidel[m]>
dannycarrera: if you use Firefox: about:debugging#/runtime/this-firefox → IPFS Companion → Inspect
<lidel[m]>
you will get console + network tab + debugger for webextension context
<dannycarrera>
Thanks lidel[m] I got that far
<dannycarrera>
Is there a way to not have the js files bundled?
<dannycarrera>
or step through in my IDE? (vscode)
<lidel[m]>
release version is minified and source maps are stripped, so if you want to debug meaningful code you need to build debug version of the bundles via `npm run watch` and then load it manually via `npm run firefox:nightly` – https://github.com/ipfs-shipyard/ipfs-companion/blob/master/DEVELOPER-NOTES.md
<lidel[m]>
dannycarrera: anything specific you want to debug? if you want to debug redirects, then you probably want to put breakpoints in `ipfs-request.js`, most of webRequest hooks are there
slack1256 has joined #ipfs
<dannycarrera>
lidel[m]: I wanted to get acquainted with how ipfs-companion works, specifically how it captures a url and connects to an ipfs node to server data
<slack1256>
dannycarrera: Man, I was going to ask exactly that. I was ready to press enter.
<dannycarrera>
I started making my way through `ipfs-request.js` and wanted to setup breakpoints to see the whole lifecycle
<slack1256>
I was searching the logs of this channel, but it returned a 502.
jadedctrl has joined #ipfs
<dannycarrera>
im a total newb to this and IRC ><
<dannycarrera>
slack1256 how do you @ people here?
<slack1256>
I want to know how to do what the ipfs-companion does but from the webui, manually if you say so.
<slack1256>
dannycarrera: I prefix their name onto the message and expect their clients will trigger a popup.
<lidel[m]>
dannycarrera: If you want to save time, I believe reading https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/webRequest will give you mental model of the request lifecycle hooks we have to our disposal in a generic browser extension, then you can see hooks for each stage in ipfs-companion's `ipfs-request.js`
stoopkid has quit [Quit: Connection closed for inactivity]
<dannycarrera>
lidel[m] Thanks so much! That's exactly what I was looking for. I'm able to see the source files in firefox now with `npm run watch` and `npm run firefox:nightly`