dependencies pragma parsing is too strict

[pablochacin]

The Automatic dependency resolution supports the definition of dependency pragmas that define version constraints for the dependencies. The format is use k6 with <dependency>< constraints>

Currently, k6 parses this pragma only if the constraints are separated by a space from the dependency name:

"use k6 with k6/x/faker =v0.4.4"; ✔️
"use k6 with k6/x/faker=v0.4.4"; ❌

For example, running this script:

"use k6 with k6/x/faker=v0.4.0"; 

import faker from "k6/x/faker";

export default function () {
  console.log(faker.person.name());
}

Produces the following error:

ERRO[0000] Failed to provision a k6 binary with required dependencies. Please, make sure to report this issue by opening a bug report.  error="invalid build parameters: unknown dependency : k6/x/faker=v0.4.0"

[mstoykov]

the specification of dependency pragmas

Can you show me this specification?

[pablochacin]

@mstoykov As far as I know, there's no formal (standard) specification. I edited the issue to "definition" to avoid confusion.

Regardless of this, I think it is not a great user experience that this space makes a difference.

[mstoykov]

I would consider this an enhancment at this point given the lack of reports from end users, and the fact that we went through multiple reviews and testing and nobody found this out.

I am not against it being parsable without a space, but will not prioritize it high as a bug or something.

I also will recommend that we have this better documented and tested

[mstoykov]

and for the record AFAIK there is no constraint on symbols in module names ... so k6/x/faker> is AFAIK a proper module name that someone can have.