Mihail Stoykov

I would prefer for us to try and see if it is goign to be brittle. In general k6 master if pretty stable - if something starts breaking, this likely...

This repo doesn't build *with* tsc directly but with `webpack`. You can look at the documentation. And webpack specifically doesn't look into `https://` imports as they are usually not supported....

@oleiade do we want to get this in our code as well?

After over a week it seems like the agreement is to have this as an exception instead of warning. You can do that by returning an error - Sobek (the...

:wave: @vincentandreas Please rebase on latest master as https://github.com/grafana/k6/pull/4701 is needed to see if the test are working. This was the problem we were having but now it should fail...

Hi @vincentandreas , first - thank you for the work you have done :bow: This PR has been open for a while now. We would like to get a fix...

I will close this PR, due to inactivity :( Thank you for bringing this up and helping figureing out the correct approach. Given the low priority of the issue and...

Not certain if this is actually required but the current warning is quite big, and I expect maybe in the future it will be an error. And it confuses the...

This likely *is not* ready to be merged and as there are 2 others ongoing PRs I will likely wait for them to be merged before I push this forward....

> from the repo, not the npm packages From my experience my neovim just does it (with tsserver obviously) as long as I am inside the `types/k6`. Also obviously running...