Fix initiator and update package lock

[ddadon10]

Hello,

I fixed the initiator, its now have different properties according to its type property:

For all type:

• detail (serialized version of the whole initiator object)
• type (script, parser or other)

Parser type:

• url
• line number

Script type:

• url of the top element in the call frame
• line number of the top element in the call frame
• column number of the top element in the call frame
• function's name of the top element in the call frame
• script's id of the top element in the call frame

And I updated the package.lock.json

Thanks 😄

[ddadon10]

Strange, npm run lint do not raise me any error on my machine, do I miss something ?

[ddadon10]

Also, I found that the CI has failed with the precedent commit https://travis-ci.org/sitespeedio/chrome-har/jobs/322701738 too.

Do I have to change something in the code or does the CI criteria (or the linter in the code) have to be change ?

Thanks 😄

[tobli]

This is also 0-based, right?

[ddadon10]

Idk, will check 😄

[ddadon10]

Yes it's 0 based https://chromedevtools.github.io/devtools-protocol/1-2/Runtime#type-CallFrame

Will commit the fix

[tobli]

Since we don’t lock down dev dependencies, the version of prettier that’s the current at the time will be run. There are sometimes small formatting changes to prettier, so a previously green build might shift to red, just by running npm install at a later time. Not ideal, we should probably lock it down, at least to a major version.

I can have a closer look, hopefully later tonight. Changes look awesome btw. =)