feat: migrate assets related to initial setup and configuration from @wdio/cli#855
feat: migrate assets related to initial setup and configuration from @wdio/cli#855mato533 wants to merge 13 commits intowebdriverio:mainfrom
Conversation
christian-bromann
left a comment
There was a problem hiding this comment.
Let's introduce a proper bundler for this. It may also be helpful to have independent exports for the vscode environment
scripts/copy.ts
Outdated
| @@ -0,0 +1,50 @@ | |||
| import fg from 'fast-glob' | |||
There was a problem hiding this comment.
Let's not use a script for that, instead use a Vite plugin
There was a problem hiding this comment.
Oh I see, we don't have this here, then it makes sense to have it. Let's use https://rolldown.rs/ for bundling instead of raw TS and include this as part of the build step.
There was a problem hiding this comment.
I agree with bundling by rolldown! I think leveraging the rollup ecosystem and esbuild's speed will open up new possibilities.
I will push the update later.
There was a problem hiding this comment.
@christian-bromann
I have pushed some changes which introduce rolldown configurations.
christian-bromann
left a comment
There was a problem hiding this comment.
LGTM 👍
We should make sure that we update our documentation at some point.
|
finding the point of wrote down... BTW, there is no confirmation, moving resources to the create-wdio side seems to pose a potential risk of incompatibility with the webdriverio side version. Specifically, when running the slightly older @wdio/cli and when create-wdio is installed in a new version, services that are not supported by the old webdriverio will be displayed as options. As a countermeasure, I think it would be best to incorporate create-wdio as a subpackage of the webdriverio repository so that version management can be performed as a single unit. What do you think about this idea? |
Makes totally sense, good call! Let's do that! |
Description
Review the functional configuration between @wdio/cli and create-wdio.
In particular, transfer functions such as initial settings, services, and framework installation to this package.
The goal is to facilitate integration with interfaces other than cli (such as vscode).
In this PR, we will not make any major modifications, but rather aim to establish integration with @wdio/cli by porting the assets of the current @wdio/cli as-is as much as possible.
Remarks
We plan to perform maintenance such as improvements for integration with interfaces other than CLI and improvements to unit tests in a separate PR.