chenglou changed the topic of #reasonml to: facebook.github.io/reason/. Public channel logs at irclog.whitequark.org/reasonml. Discord: discord.gg/reasonml
peterhil has quit [Read error: Connection reset by peer]
peterhil has joined #reasonml
Mikk36 has quit [Ping timeout: 268 seconds]
Mikk36 has joined #reasonml
andreas__ has quit [Quit: Connection closed for inactivity]
nomicflux has joined #reasonml
nomicflux has quit [Quit: nomicflux]
xkapastel has quit [Quit: Connection closed for inactivity]
andreas__ has joined #reasonml
<magopian> hi, I'm having an issue this morning with "npm start", it was working fine yesterday, but I rebooted to have the latest osx version (0.13.1 instead of 0.13.0 I believe), and now i'm having https://dpaste.de/hP94
<magopian> does it ring a bell to anyone?
<magopian> i'm following https://jaredforsyth.com/2017/07/05/a-reason-react-tutorial/ and it worked perfectly yesterday
<reynir> -.-
<reynir> No idea, good luck magopian :/
<magopian> well, I'll find out eventually, thanks reynir ;)
<reynir> It's never been a pleasant experience for me dealing with errors from npm heh
<magopian> ok, removing the node_modules folder and doing a "npm install" again fixed it, go figure
<magopian> the good thing about npm errors is that they're often fixed by reinstalling :P
<reynir> heh
<reynir> The "have you tried turning it off and on again?" of package managers :P
<magopian> :P
<chenglou> @magopian you might have touched node_modules somehow in-between
<magopian> not on purpose, but maybe :P
<chenglou> ENOENT means doesn't exist
dywedir has joined #reasonml
<magopian> oh, ok, thanks
<magopian> so somehow, something got erased, or moved
<chenglou> which version of npm are you on btw?
<magopian> 5.4.2
<chenglou> k, that one should be fine at least
<magopian> a question that might more be react related than reason(react) related: I'm following https://jaredforsyth.com/2017/07/05/a-reason-react-tutorial/ and at some point we add a "key" attribute to the components created in a List.map (specifically in https://jaredforsyth.com/2017/07/05/a-reason-react-tutorial/#18-tracking-ids-w-a-mutable-ref-)
<magopian> however, it seems the key isn't really used: it's passed as a "prop" to the TodoItem component, but then this component doesn't actually do anything with it (like adding a "key" attribute to the div ?)
<magopian> isn't it useful? Is it only in the virtual dom that it's used maybe, and so it doesn't need to end up in the DOM ?
nomicflux has joined #reasonml
nomicflux has quit [Quit: nomicflux]
nomicflux has joined #reasonml
nomicflux has quit [Quit: nomicflux]
andreas__ has quit [Quit: Connection closed for inactivity]
_whitelogger has joined #reasonml
rostero has joined #reasonml
andreas__ has joined #reasonml
xkapastel has joined #reasonml
rostero has quit [Quit: Connection closed for inactivity]
<chenglou> @magopian ah, so that part requires a bit of prior ReactJS knowledge. `key` and `ref` are special "props" in ReactJS
dywedir has quit [Remote host closed the connection]
littleli has joined #reasonml