@geops/rvf-mobility-web-component 0.1.121 → 0.1.123
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/CHANGELOG.md +14 -0
- package/README.md +0 -7
- package/index.js +119971 -1439
- package/package.json +2 -2
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,20 @@
|
|
|
2
2
|
|
|
3
3
|
All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines.
|
|
4
4
|
|
|
5
|
+
### [0.1.123](https://github.com/geops/rvf-mobility-web-component/compare/v0.1.122...v0.1.123) (2026-03-05)
|
|
6
|
+
|
|
7
|
+
|
|
8
|
+
### Bug Fixes
|
|
9
|
+
|
|
10
|
+
* update mbt ([5fd8d80](https://github.com/geops/rvf-mobility-web-component/commit/5fd8d80fcd00a2e0ee2e91e26b2ed390732261a0))
|
|
11
|
+
|
|
12
|
+
### [0.1.122](https://github.com/geops/rvf-mobility-web-component/compare/v0.1.121...v0.1.122) (2026-03-05)
|
|
13
|
+
|
|
14
|
+
|
|
15
|
+
### Bug Fixes
|
|
16
|
+
|
|
17
|
+
* revert update of mbt ([645d9c8](https://github.com/geops/rvf-mobility-web-component/commit/645d9c83acc8f4f2a087caf7ce39e00951047edb))
|
|
18
|
+
|
|
5
19
|
### [0.1.121](https://github.com/geops/rvf-mobility-web-component/compare/v0.1.120...v0.1.121) (2026-03-05)
|
|
6
20
|
|
|
7
21
|
|
package/README.md
CHANGED
|
@@ -48,17 +48,11 @@ yarn start
|
|
|
48
48
|
|
|
49
49
|
The [Vercel app](https://rvf-mobility-web-component-geops.vercel.app/) is the official documentation for the customer, make sure it is up to date and exhaustive. The deploy is automatic with every merge on `main` branch.
|
|
50
50
|
|
|
51
|
-
<<<<<<< HEAD
|
|
52
51
|
In production RVF uses the latest NPM package [@geops/rvf-mobility-web-component](https://www.npmjs.com/package/@geops/rvf-mobility-web-component) so to push something to production you have to publish a new version using:
|
|
53
52
|
|
|
54
53
|
```bash
|
|
55
54
|
yarn publish
|
|
56
55
|
```
|
|
57
|
-
=======
|
|
58
|
-
The Vite build, used for development, is also deployed on [https://main-mobility-web-component.vercel.app/](https://main-mobility-web-component.vercel.app/).
|
|
59
|
-
|
|
60
|
-
For forked project, the static index.html file is enough as documentation for the client. No need to provide the NextJS documentation website.
|
|
61
|
-
Just set it up properly in vercel. See [RVF configuration](https://vercel.com/geops/rvf-mobility-web-component) for an example.
|
|
62
56
|
|
|
63
57
|
## Guidelines
|
|
64
58
|
|
|
@@ -84,7 +78,6 @@ At this point you're ready to create custom code, some rules must be followed to
|
|
|
84
78
|
- never modify the original components in the forked repository, do it in the upstream repository then merge it in the forked repository.
|
|
85
79
|
- never update dependencies in the forked repository, do it in the upstream repository then merge it in the forked repository.
|
|
86
80
|
- if you have a doubt, ask.
|
|
87
|
-
>>>>>>> upstream/main
|
|
88
81
|
|
|
89
82
|
## Merge upstream repository
|
|
90
83
|
|