gc_i18n 1.5.4 → 1.5.5
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/AGENTS.md +24 -0
- package/lang/index.json +4 -0
- package/lib/gc_i18n.es.js +734 -709
- package/lib/gc_i18n.umd.js +41 -41
- package/package.json +1 -1
- package/packages/index.js +35 -11
- package/packages/libs/service.js +43 -37
package/AGENTS.md
ADDED
|
@@ -0,0 +1,24 @@
|
|
|
1
|
+
# Repository Guidelines
|
|
2
|
+
|
|
3
|
+
## Project Structure & Module Organization
|
|
4
|
+
`packages/` contains the published library source: `index.js` is the main entry, `libs/` holds utilities and services, and `components/` contains reusable UI pieces. `src/` is the local Vite playground used to exercise the plugin in a Vue app, with routes in `src/router/` and views in `src/view/`. `lang/` stores bundled language data. `example/vue2-test/` and `example/vue3-test/` are manual integration fixtures. `lib/` contains build artifacts and should only change when releasing a new build.
|
|
5
|
+
|
|
6
|
+
## Build, Test, and Development Commands
|
|
7
|
+
Prefer `pnpm` because the repo declares `pnpm@10` and includes a workspace file.
|
|
8
|
+
|
|
9
|
+
- `pnpm dev`: start the local Vite playground.
|
|
10
|
+
- `pnpm dev:unit`: run the playground in `unit` mode on port `8080`.
|
|
11
|
+
- `pnpm dev:template`: run the template mode on port `8081`.
|
|
12
|
+
- `pnpm build`: generate library bundles in `lib/`.
|
|
13
|
+
- `pnpm preview`: preview the latest production build.
|
|
14
|
+
- `cd example/vue3-test && pnpm dev`: verify Vue 3 integration.
|
|
15
|
+
- `cd example/vue2-test && pnpm dev`: verify Vue 2 integration.
|
|
16
|
+
|
|
17
|
+
## Coding Style & Naming Conventions
|
|
18
|
+
Match the style of the file you touch. In current source, prefer double quotes, semicolons, and descriptive camelCase names for variables and functions. Use PascalCase for Vue components such as `Home.vue`, and keep utility modules in lowercase filenames such as `service.js` or `i18nUtils.ts`. Default to 2-space indentation in Vue/JS files unless the target file already uses a different width.
|
|
19
|
+
|
|
20
|
+
## Testing Guidelines
|
|
21
|
+
There is no automated unit test suite configured in the root package. Validate changes by running `pnpm build` and manually exercising the Vue 2 and Vue 3 examples, especially `$t()`, locale switching, router integration, and keyboard-triggered flows. Keep example-specific notes in `example/TEST_REPORT.md` when behavior or compatibility changes.
|
|
22
|
+
|
|
23
|
+
## Commit & Pull Request Guidelines
|
|
24
|
+
Recent history uses short conventional prefixes: `feat:`, `fix:`, and `build:`. Follow that format and keep subjects brief, for example `fix: normalize Firefox locale handling`. Pull requests should state the user-facing change, list verification steps, and include screenshots or recordings for UI or modal changes. Call out any regenerated `lib/` files so reviewers can separate source edits from build output.
|