fix(nonGlobalStepDefinitions): .features files now work with webpack

[sebastiandero]

I have tried with our project (80+ scenarios) they now seem to work.

tests in the repo also pass (some dont because of windows vs linux path slashes, but that was the case before)

#304

[badeball]

It seems like this conditionally removes the cache busting in case Weback is detected. The cache busting is however important and serves a particular purposes when using nonGlobalStepDefinitions: true. Are you using it with true or false?

[sebastiandero]

@badeball

{
    "stepDefinitions": "src/integration",
    "nonGlobalStepDefinitions": true
}

this is what i tested with

EDIT: here's what I based my test on ->

What actually happens here I believe is we need to make sure that importing the same file twice runs it's side effects, instead of just getting the cached export otherwise if you use the same file in nonGlobal feature things are not working right. It'd be easy to test by making that clearFromCache function empty and seeing how webpack behaves - maybe things will just work? (although I doubt it)

[sebastiandero]

@badeball i've just encountered some weird behavior, let me have another look

[sebastiandero]

@badeball if you could do another review, that would be awesome, im now deleting the moduleid entry from require.cache

[badeball]

The current state of things is indeed how I imagined it would be. Did it solve the problem you mentioned above?

[sebastiandero]

@badeball yes it did, now tests run as expected.

[lgandecki]

Thanks so much for the PR @sebastiandero , glad you got it.
Also, thanks @badeball for a spot on review :-)

[lgandecki]

🎉 This PR is included in version 2.5.2 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀