@eclipse-scout/migrate 25.1.0-beta.0 → 25.1.0-beta.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +4 -4
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -24,7 +24,7 @@ To set up the tool, do the following:
|
|
|
24
24
|
- Add a devDependency to `@eclipse-scout/migrate`.
|
|
25
25
|
- Run `pnpm install` to install the new dependency.
|
|
26
26
|
- Do the required migration as described in the following chapters.
|
|
27
|
-
- When you are finished, remove the added dependency and migration script from
|
|
27
|
+
- When you are finished, remove the added dependency and migration script from your `package.json`.
|
|
28
28
|
|
|
29
29
|
```json
|
|
30
30
|
{
|
|
@@ -119,7 +119,7 @@ In order to run the TypeScript migration, do the following:
|
|
|
119
119
|
- Ensure you have a clean Git working tree (no uncommitted files).
|
|
120
120
|
- Create a `tsconfig.json` as described [here](#tsconfig)
|
|
121
121
|
- Add scripts in your `package.json` as described below.
|
|
122
|
-
- Add an `override` in your `package.json` to fix the TypeScript version to 5.
|
|
122
|
+
- Add an `override` in your `package.json` to fix the TypeScript version to 5.4.5 (the migrate tool will skip some migrations and print a warning about the wrong version otherwise). This is only needed for the migration and has to be
|
|
123
123
|
removed afterwards.
|
|
124
124
|
- Adjust the module map as described in the chapter [Module Map](#module-map)
|
|
125
125
|
- Add custom type maps if you have a large code base and would like to automate a little more, see [Type Map](#type-map)
|
|
@@ -138,7 +138,7 @@ In order to run the TypeScript migration, do the following:
|
|
|
138
138
|
In your widget, implement the model interface and declare a model variable.
|
|
139
139
|
- To create the event maps, you can run the `event-maps` script from below and copy the result into a separate event maps file.
|
|
140
140
|
- If you use third party libraries, you may want to check if they provide types and add them to the `devDependencies` of your `package.json` (e.g. @types/jquery).
|
|
141
|
-
See also [Project Setup for TypeScript](https://eclipsescout.github.io/scout-docs/
|
|
141
|
+
See also [Project Setup for TypeScript](https://eclipsescout.github.io/scout-docs/25.1/technical-guide/user-interface/typescript.html#project-setup-for-typescript)
|
|
142
142
|
- Remove the added `scripts`, `overrides` and dependency to `@eclipse-scout/migrate`.
|
|
143
143
|
|
|
144
144
|
```json
|
|
@@ -215,5 +215,5 @@ For the TypeScript migration, you can do it as follows:
|
|
|
215
215
|
}
|
|
216
216
|
```
|
|
217
217
|
|
|
218
|
-
**Note**: you can either define the module map in the config file or pass it
|
|
218
|
+
**Note**: you can either define the module map in the config file or pass it as arguments to the script.
|
|
219
219
|
If you do both, they will be merged. If they contain the same keys, the value passed via argument wins.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@eclipse-scout/migrate",
|
|
3
|
-
"version": "25.1.0-beta.
|
|
3
|
+
"version": "25.1.0-beta.2",
|
|
4
4
|
"description": "TypeScript migration module",
|
|
5
5
|
"author": "BSI Business Systems Integration AG",
|
|
6
6
|
"homepage": "https://eclipse.dev/scout/",
|
|
@@ -42,7 +42,7 @@
|
|
|
42
42
|
"jest": "29.7.0",
|
|
43
43
|
"@babel/preset-env": "7.26.0",
|
|
44
44
|
"@babel/core": "7.26.0",
|
|
45
|
-
"@eclipse-scout/tsconfig": "25.1.0-beta.
|
|
45
|
+
"@eclipse-scout/tsconfig": "25.1.0-beta.2"
|
|
46
46
|
},
|
|
47
47
|
"scripts": {
|
|
48
48
|
"scout-migrate": "node bin/scout-migrate",
|