You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I initialized wdio in my project, selecting TypeScript as compiler, the CLI created a wdio.config.ts (config file in TypeScript). This is fine, but at the same time, it added a npm script to package.json which refers to wdio.config.js (config file in JavaScript).
It also didn't take into account, where the wdio.config.js/ts was located. Even though I used default values for the initialization (expect using Jasmine and TypeScript), it thought my wdio.config.js/ts was located in the root of the project, but itself created it in ./test/.
What is your expected behavior?
I expected that the CLI would know what file extension the wdio config would have, and where it would be created, so the npm script in package.json would be correct.
How to reproduce the bug.
I ran npm init wdio .
Used default values for the questions except for the following:
Which framework do you want to use? jasmine
Do you want to use a compiler? TypeScript
Now the npm script in package.json would be "wdio": "wdio run wdio.conf.js"
Any contributions that resolves the bug are highly appreciated. Please take a look into our contribution guidelines and let us know if you have any questions. Cheers!
Have you read the Contributing Guidelines on issues?
WebdriverIO Version
7.16.13
Node.js Version
14.18.2
Mode
Standalone Mode
Which capabilities are you using?
No response
What happened?
When I initialized wdio in my project, selecting TypeScript as compiler, the CLI created a
wdio.config.ts
(config file in TypeScript). This is fine, but at the same time, it added a npm script topackage.json
which refers towdio.config.js
(config file in JavaScript).It also didn't take into account, where the
wdio.config.js/ts
was located. Even though I used default values for the initialization (expect using Jasmine and TypeScript), it thought mywdio.config.js/ts
was located in the root of the project, but itself created it in./test/
.What is your expected behavior?
I expected that the CLI would know what file extension the wdio config would have, and where it would be created, so the npm script in
package.json
would be correct.How to reproduce the bug.
npm init wdio .
jasmine
TypeScript
package.json
would be"wdio": "wdio run wdio.conf.js"
Relevant log output
Code of Conduct
Is there an existing issue for this?
The text was updated successfully, but these errors were encountered: