@omicronenergy/oscd-shell 0.0.5 → 0.0.8

package/.github/actions/setup-node-env/action.yml

@@ -1,49 +0,0 @@
-name: 'Setup Node Environment'
-description: 'Setup Node, cache and clean install'
-
-inputs:
-  registry-url:
-    description: 'the url for the registry (github or npm)'
-    required: false
-    default: 'https://registry.npmjs.org'
-
-runs:
-  using: composite
-  steps:
-    - name: Set up Node.js
-      uses: actions/setup-node@v3
-      with:
-        node-version: '20'
-        registry-url: ${{ inputs.registry-url }}
-
-    - name: Cache Node Modules
-      id: cache-node-modules
-      uses: actions/cache@v4
-      with:
-        path: |
-          node_modules
-        key: modules-${{ hashFiles('package-lock.json') }}
-
-    - name: Cache Playwright Binaries
-      id: cache-playwright
-      uses: actions/cache@v4
-      with:
-        path: |
-          ~/.cache/ms-playwright
-        key: playwright-${{ hashFiles('package-lock.json') }}
-
-    - name: Install dependencies
-      if: steps.cache-node-modules.outputs.cache-hit != 'true'
-      run: npm ci
-      shell: bash
-
-    - name: Install playwright browsers
-      if: steps.cache-playwright.outputs.cache-hit != 'true'
-      run: npx playwright install --with-deps
-      shell: bash
-
-    - name: Install system dependencies for WebKit
-      # Some WebKit dependencies seem to lay outside the cache and will need to be installed separately
-      if: steps.cache-playwright.outputs.cache-hit == 'true'
-      run: npx playwright install-deps webkit
-      shell: bash

package/.github/workflows/release-please.yml

@@ -1,84 +0,0 @@
-name: release-please
-
-on:
-  push:
-    branches:
-      - main
-
-jobs:
-  release-please:
-    runs-on: ubuntu-latest
-    outputs:
-      release_created: ${{ steps.release.outputs.release_created }}
-      tag_name: ${{ steps.release.outputs.tag_name }}
-    permissions:
-      contents: write
-      pull-requests: write
-      issues: write
-    steps:
-      - uses: googleapis/release-please-action@v4
-        id: release
-        with:
-          token: ${{ secrets.GITHUB_TOKEN }}
-          config-file: release-please-config.json
-          manifest-file: .release-please-manifest.json
-
-  add-build-artifact-to-release:
-    needs: release-please
-    if: ${{ needs.release-please.outputs.release_created }}
-    runs-on: ubuntu-latest
-    permissions:
-      contents: write
-      pages: write
-    steps:
-      - uses: actions/checkout@v4
-      - uses: ./.github/actions/setup-node-env
-
-      - name: Build
-        run: npm run build
-
-      - name: Compress build output
-        run: |
-          (cd ./dist && zip -r ../oscd-shell.zip .)
-          tar -C ./dist -czvf oscd-shell.tar.gz ./
-
-      - name: Upload Compressed files
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-        run: gh release upload ${{ needs.release-please.outputs.tag_name }} oscd-shell.zip oscd-shell.tar.gz
-
-  npm-publish:
-    needs: release-please
-    if: ${{ needs.release-please.outputs.release_created }}
-    runs-on: ubuntu-latest
-    permissions:
-      contents: read
-      id-token: write
-    steps:
-      - uses: actions/checkout@v4
-      - uses: ./.github/actions/setup-node-env
-        with:
-          registry-url: 'https://registry.npmjs.org'
-      - run: npm publish --provenance --access public
-        env:
-          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
-
-  deploy:
-    needs: release-please
-    if: ${{ needs.release-please.outputs.release_created }}
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v4
-
-      - uses: ./.github/actions/setup-node-env
-
-      - name: Build
-        run: npm run bundle
-
-      - name: Deploy
-        run: |
-          git remote set-url origin https://git:${GITHUB_TOKEN}@github.com/${GITHUB_REPOSITORY}.git
-          npx gh-pages -d dist -u "github-actions <support+actions@github.com>"
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

package/.github/workflows/test.yml

@@ -1,18 +0,0 @@
-name: Test
-on: [push, pull_request, workflow_dispatch]
-
-jobs:
-  test:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v4
-
-      - uses: ./.github/actions/setup-node-env
-
-      - name: Run unit tests
-        run: npm run-script test:unit
-
-      - name: Run visual regression tests on PR
-        if: github.event_name == 'pull_request' || github.event_name == 'workflow_dispatch'
-        run: npm run-script test:visual

package/.github/workflows/update-screenshots.yml

@@ -1,29 +0,0 @@
-name: Update Screenshots
-
-on: [push, workflow_dispatch]
-
-jobs:
-  update-screenshots:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v4
-        with:
-          ref: ${{ github.head_ref }}
-
-      - uses: ./.github/actions/setup-node-env
-
-      - name: Run visual regression tests
-        run: npm run test:visual
-        id: tests
-        continue-on-error: true
-
-      - name: Update screenshots
-        if: ${{ steps.tests.outcome == 'failure' }}
-        run: |
-          npm run test:update
-          git config --global user.name "github-actions[bot]"
-          git config --global user.email "41898282+github-actions[bot]@users.noreply.github.com"
-          git add screenshots
-          git commit -m "test: update screenshots"
-          git push

package/.husky/commit-msg

@@ -1 +0,0 @@
-npx --no -- commitlint --edit $1

package/.husky/pre-commit

@@ -1 +0,0 @@
-npx lint-staged

package/.release-please-manifest.json

@@ -1 +0,0 @@
-{".":"0.0.5"}

package/CHANGELOG.md

@@ -1,73 +0,0 @@
-# Changelog
-
-## [0.0.5](https://github.com/OMICRONEnergyOSS/oscd-shell/compare/oscd-shell-v0.0.4...oscd-shell-v0.0.5) (2025-06-11)
-
-
-### Features
-
-* add theming ([9f44494](https://github.com/OMICRONEnergyOSS/oscd-shell/commit/9f4449421ca1f8e6b2ea0225bf8f25dbf3163b99))
-* add UpdateNS edit type ([4e36a57](https://github.com/OMICRONEnergyOSS/oscd-shell/commit/4e36a575e468aa9867050ddc0b4402494e4a6205))
-* **demo:** add remote open and save plugins ([798fc93](https://github.com/OMICRONEnergyOSS/oscd-shell/commit/798fc93333408bf56d350e5130734c5d60d5657c))
-* edit multiple open files ([88bd287](https://github.com/OMICRONEnergyOSS/oscd-shell/commit/88bd2878e093763d4d848ed2dd0a0baa8421ae47))
-* **editing:** add editing user interface elements ([e834e4d](https://github.com/OMICRONEnergyOSS/oscd-shell/commit/e834e4d0853e3cd2e2a2ce9d74120c4d06ce92bd))
-* **editing:** insert and remove nodes ([65c99da](https://github.com/OMICRONEnergyOSS/oscd-shell/commit/65c99da931aa88c527504a362353da0ac443a23e))
-* **editing:** open documents ([e3a3199](https://github.com/OMICRONEnergyOSS/oscd-shell/commit/e3a31999046a29a7aa44467f9b7a7fde784b982f))
-* **editing:** update elements' attributes ([b29eff0](https://github.com/OMICRONEnergyOSS/oscd-shell/commit/b29eff04cdc9d14d9f002f183eeb51f7f6adaac9))
-* export open-scd and mixin types ([5415d2b](https://github.com/OMICRONEnergyOSS/oscd-shell/commit/5415d2b283e15870fb3d4eec32ec630fd174b28b))
-* **foundation:** export cyrb64 hash function ([5b13d94](https://github.com/OMICRONEnergyOSS/oscd-shell/commit/5b13d9466becc2f0922164b806f77d8f01a234ab))
-* migrated UI to new oscd-ui ([ae99e24](https://github.com/OMICRONEnergyOSS/oscd-shell/commit/ae99e24fda427e81bfd6088f5889ea44aa410478))
-* **open-scd:** pass editCount to editor and menu plugins ([2be53ab](https://github.com/OMICRONEnergyOSS/oscd-shell/commit/2be53ab8de8bad176097153240441db521b99ce8))
-* **plugging:** load menu and editor plugins ([e3fe982](https://github.com/OMICRONEnergyOSS/oscd-shell/commit/e3fe98223cefd7b3a9abd49c444f5bfba3c527a8))
-* switch shell to using scoped components ([4ec3ffa](https://github.com/OMICRONEnergyOSS/oscd-shell/commit/4ec3ffa2fa9a454646bcda314abe168da6693337))
-
-
-### Bug Fixes
-
-* **open-scd:** allow menu plugins to show content ([c7dc849](https://github.com/OMICRONEnergyOSS/oscd-shell/commit/c7dc849fa84419ab605ffafd2b0ec7ce40136fc3))
-* **open-scd:** hide menu plugin element container ([02b026e](https://github.com/OMICRONEnergyOSS/oscd-shell/commit/02b026e645ebfa9c26f54afd5f292a10b56af7ef))
-* **open-scd:** import locales from relative URL ([5877314](https://github.com/OMICRONEnergyOSS/oscd-shell/commit/5877314f5e2de4c3613324e51328cb463dec2d5d))
-* **package:** localize as part of bundle script ([653a506](https://github.com/OMICRONEnergyOSS/oscd-shell/commit/653a50667163e9a9381d26ccb10e927f0758ec73))
-* **plugging:** import relative paths from origin ([abb5074](https://github.com/OMICRONEnergyOSS/oscd-shell/commit/abb50749877ce611e4eb58bcde2e39280c429150))
-
-
-### Styles
-
-* disable quirks mode in demo and tests ([db1b6c8](https://github.com/OMICRONEnergyOSS/oscd-shell/commit/db1b6c858a97f6842526aa624311d9d1842dfc49))
-
-## [0.0.4](https://github.com/OMICRONEnergyOSS/open-scd-core/compare/open-scd-core-v0.0.3...open-scd-core-v0.0.4) (2025-04-22)
-
-
-### Bug Fixes
-
-* **package:** localize as part of bundle script ([653a506](https://github.com/OMICRONEnergyOSS/open-scd-core/commit/653a50667163e9a9381d26ccb10e927f0758ec73))
-
-## [0.0.3](https://github.com/OMICRONEnergyOSS/open-scd-core/compare/open-scd-core-v0.0.2...open-scd-core-v0.0.3) (2025-04-22)
-
-
-### Features
-
-* add theming ([9f44494](https://github.com/OMICRONEnergyOSS/open-scd-core/commit/9f4449421ca1f8e6b2ea0225bf8f25dbf3163b99))
-* add UpdateNS edit type ([4e36a57](https://github.com/OMICRONEnergyOSS/open-scd-core/commit/4e36a575e468aa9867050ddc0b4402494e4a6205))
-* **demo:** add remote open and save plugins ([798fc93](https://github.com/OMICRONEnergyOSS/open-scd-core/commit/798fc93333408bf56d350e5130734c5d60d5657c))
-* edit multiple open files ([88bd287](https://github.com/OMICRONEnergyOSS/open-scd-core/commit/88bd2878e093763d4d848ed2dd0a0baa8421ae47))
-* **editing:** add editing user interface elements ([e834e4d](https://github.com/OMICRONEnergyOSS/open-scd-core/commit/e834e4d0853e3cd2e2a2ce9d74120c4d06ce92bd))
-* **editing:** insert and remove nodes ([65c99da](https://github.com/OMICRONEnergyOSS/open-scd-core/commit/65c99da931aa88c527504a362353da0ac443a23e))
-* **editing:** open documents ([e3a3199](https://github.com/OMICRONEnergyOSS/open-scd-core/commit/e3a31999046a29a7aa44467f9b7a7fde784b982f))
-* **editing:** update elements' attributes ([b29eff0](https://github.com/OMICRONEnergyOSS/open-scd-core/commit/b29eff04cdc9d14d9f002f183eeb51f7f6adaac9))
-* export open-scd and mixin types ([5415d2b](https://github.com/OMICRONEnergyOSS/open-scd-core/commit/5415d2b283e15870fb3d4eec32ec630fd174b28b))
-* **foundation:** export cyrb64 hash function ([5b13d94](https://github.com/OMICRONEnergyOSS/open-scd-core/commit/5b13d9466becc2f0922164b806f77d8f01a234ab))
-* **open-scd:** pass editCount to editor and menu plugins ([2be53ab](https://github.com/OMICRONEnergyOSS/open-scd-core/commit/2be53ab8de8bad176097153240441db521b99ce8))
-* **plugging:** load menu and editor plugins ([e3fe982](https://github.com/OMICRONEnergyOSS/open-scd-core/commit/e3fe98223cefd7b3a9abd49c444f5bfba3c527a8))
-
-
-### Bug Fixes
-
-* **open-scd:** allow menu plugins to show content ([c7dc849](https://github.com/OMICRONEnergyOSS/open-scd-core/commit/c7dc849fa84419ab605ffafd2b0ec7ce40136fc3))
-* **open-scd:** hide menu plugin element container ([02b026e](https://github.com/OMICRONEnergyOSS/open-scd-core/commit/02b026e645ebfa9c26f54afd5f292a10b56af7ef))
-* **open-scd:** import locales from relative URL ([5877314](https://github.com/OMICRONEnergyOSS/open-scd-core/commit/5877314f5e2de4c3613324e51328cb463dec2d5d))
-* **plugging:** import relative paths from origin ([abb5074](https://github.com/OMICRONEnergyOSS/open-scd-core/commit/abb50749877ce611e4eb58bcde2e39280c429150))
-
-
-### Styles
-
-* disable quirks mode in demo and tests ([db1b6c8](https://github.com/OMICRONEnergyOSS/open-scd-core/commit/db1b6c858a97f6842526aa624311d9d1842dfc49))

package/CONTRIBUTING.md

@@ -1,393 +0,0 @@
-# Contributing to OpenSCD Core
-
-Thanks for taking the time to contribute to the OpenSCD project!
-
-## Non-Code Contributions
-
-You don't need to be a software developer to contribute to this effort! Apart
-from contributions in the form of code we are also very thankful for
-
-- [bug reports](https://github.com/OMICRONEnergyOSS/oscd-shell/issues?q=is%3Aopen) alerting
-  us of errors in the `oscd-shell` component or its `foundation` library
-  functions,
-- [ideas for enhancements](https://github.com/OMICRONEnergyOSS/oscd-shell/discussions/categories/ideas)
-  to `oscd-shell` or its `foundation` library,
-- [contributions to discussions](https://github.com/OMICRONEnergyOSS/oscd-shell/discussions) we're having
-  about which direction the project should take, and
-- [improvements to our wiki](https://github.com/OMICRONEnergyOSS/oscd-shell/wiki)
-  which contains knowledge about how to use both OpenSCD and SCL in general.
-
-## Code Contributions
-
-> The following is a set of guidelines for contributing to [OpenSCD
-> Core](https://github.com/OMICRONEnergyOSS/oscd-shell#readme), not a list of
-> strict rules. Use your best judgment and feel free to propose changes to this
-> document in a pull request.
-
-### Code Structure
-
-The OpenSCD Core project's [NPM package declaration file](https://github.com/OMICRONEnergyOSS/oscd-shell/blob/main/package.json) lists
-two entry points that can be referred to by package users:
-
-```json
-  "exports": {
-    ".": "dist/foundation.js",
-    "/oscd-shell.js": "dist/oscd-shell.js"
-  },
-```
-
-`foundation.ts` defines a host of types, utility functions, and constants which
-we hope will be useful for writing plugins that edit SCL files.
-
-`oscd-shell.ts` defines a custom element `<oscd-shell>`, a [web component](https://developer.mozilla.org/en-US/docs/Web/Web_Components)
-implemented as a [LitElement](https://lit.dev/docs) extended with our own
-[Mixins](https://lit.dev/docs/composition/mixins).
-
-### Commit Messages
-
-- Use the [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/)
-  format for commit messages.
-
-  > A commit should contain only one single change, so you should always be
-  > able to find a fitting type.
-
-- Use the present tense ("feat: add feature" not "feat: added feature")
-- Use the imperative mood ("fix: move cursor to..." not "fix: moves cursor
-  to...")
-- Limit the first line to 72 characters or less
-- Reference issues and pull requests liberally after the first line
-
-### Contributing Workflow and Branching Strategy
-
-We like to receive code contributions through the [Forking Workflow](https://www.atlassian.com/git/tutorials/comparing-workflows/forking-workflow),
-which means every contributor maintains their own independent fork and sends
-pull requests directly from their own copy of the repo. This enables
-contributors to work as independently as possible, with the only point of
-coordination happening when a maintainer merges the incoming pull request.
-
-A pull request should generally only ever contain at most one `fix` or `feat`
-commit, and never both. If you have several different bugs to fix or features to
-introduce, please create a separate pull request for each one. If a single bug
-fix or feature took you several commits to achieve, please squash those commits
-into one using an interactive rebase (see the great tutorial linked under
-"Forking Workflow" above) before submitting your pull request.
-
-Please make sure that all CI checks are passing before marking your pull request
-"Ready for review".
-
-### Filenames
-
-If a file defines a custom element, it should always be named after its tag name
-(e.g. `my-component.ts`). Otherwise, files should generally be named after the
-most important symbol they export (e.g. `MyClass.ts`).
-
-### Code Style and Linting
-
-We use eslint and prettier for formatting and linting. Both are run as part of
-a `husky` pre-commit hook defined in `package.json`. Nonetheless, we recommend
-you use your editor's or IED's eslint and prettier plugins for continuous
-formatting and linting while writing the code in order to avoid any surprises.
-
-Apart from the rules the linter and formatter enforce, we adopt the following
-guidelines taken from the terse but broad [Deno Style Guide](https://deno.land/manual/contributing/style_guide) with some minor adjustments:
-
-#### TODO Comments
-
-In general, don't commit TODO or FIXME comments. Their significance tends to get
-lost in the mists of time and they cause more confusion than anything else.
-
-If you are tempted to write a FIXME comment, please consider fixing the code
-immediately instead. If this is absolutely not possible, create a bug issue
-referencing your pull request which introduces the bug.
-
-If you are tempted to write a TODO comment, please consider opening an issue
-describing the changes to be made instead.
-
-If you still find it helpful to introduce a TODO comment, please include an
-issue or at least the author's github username in parentheses. Example:
-
-```ts
-// TODO(ry): Add tests.
-// TODO(#123): Support Windows.
-// FIXME(#349): Sometimes panics.
-```
-
-#### Exported functions: max 2 args, put the rest into an options object.
-
-When designing function interfaces, stick to the following rules.
-
-1. A function that is part of the public API takes 0-2 required arguments, plus
-   (if necessary) an options object (so max 3 total).
-
-2. Optional parameters should generally go into the options object.
-
-   An optional parameter that's not in an options object might be acceptable if
-   there is only one, and it seems inconceivable that we would add more optional
-   parameters in the future.
-
-3. The 'options' argument is the only argument that is a regular 'Object'.
-
-   Other arguments can be objects, but they must be distinguishable from a
-   'plain' Object runtime, by having either:
-
-   - a distinguishing prototype (e.g. `Array`, `Map`, `Date`, `class MyThing`).
-   - a well-known symbol property (e.g. an iterable with `Symbol.iterator`).
-
-   This allows the API to evolve in a backwards compatible way, even when the
-   position of the options object changes.
-
-```ts, ignore
-// BAD: optional parameters not part of options object. (#2)
-export function resolve(
-  hostname: string,
-  family?: "ipv4" | "ipv6",
-  timeout?: number,
-): IPAddress[] {}
-```
-
-```ts, ignore
-// GOOD.
-export interface ResolveOptions {
-  family?: "ipv4" | "ipv6";
-  timeout?: number;
-}
-export function resolve(
-  hostname: string,
-  options: ResolveOptions = {},
-): IPAddress[] {}
-```
-
-```ts, ignore
-export interface Environment {
-  [key: string]: string;
-}
-
-// BAD: `env` could be a regular Object and is therefore indistinguishable
-// from an options object. (#3)
-export function runShellWithEnv(cmdline: string, env: Environment): string {}
-
-// GOOD.
-export interface RunShellOptions {
-  env: Environment;
-}
-export function runShellWithEnv(
-  cmdline: string,
-  options: RunShellOptions,
-): string {}
-```
-
-```ts
-// BAD: more than 3 arguments (#1), multiple optional parameters (#2).
-export function renameSync(
-  oldname: string,
-  newname: string,
-  replaceExisting?: boolean,
-  followLinks?: boolean,
-) {}
-```
-
-```ts
-// GOOD.
-interface RenameOptions {
-  replaceExisting?: boolean;
-  followLinks?: boolean;
-}
-export function renameSync(
-  oldname: string,
-  newname: string,
-  options: RenameOptions = {},
-) {}
-```
-
-```ts
-// BAD: too many arguments. (#1)
-export function pwrite(
-  fd: number,
-  buffer: ArrayBuffer,
-  offset: number,
-  length: number,
-  position: number,
-) {}
-```
-
-```ts
-// BETTER.
-export interface PWrite {
-  fd: number;
-  buffer: ArrayBuffer;
-  offset: number;
-  length: number;
-  position: number;
-}
-export function pwrite(options: PWrite) {}
-```
-
-#### Export all interfaces that are used as parameters to an exported member
-
-Whenever you are using interfaces that are included in the parameters or return
-type of an exported member, you should export the interface that is used. Here
-is an example:
-
-```ts, ignore
-// my-file.ts
-export interface Person {
-  name: string;
-  age: number;
-}
-
-export function createPerson(name: string, age: number): Person {
-  return { name, age };
-}
-
-// mod.ts
-export { createPerson } from "./my-file.js";
-export type { Person } from "./my-file.js";
-```
-
-#### Minimize dependencies; do not make circular imports.
-
-Try not to introduce external dependencies if you can avoid doing so.
-In particular, be careful not to introduce circular imports.
-
-#### If a filename starts with an underscore: `_foo.ts`, do not link to it.
-
-There may be situations where an internal module is necessary but its API is not
-meant to be stable or linked to. In this case prefix it with an underscore. By
-convention, only files in its own directory should import it.
-
-#### Use JSDoc for exported symbols.
-
-We strive for complete documentation. Every exported symbol ideally should have
-a documentation line.
-
-If possible, use a single line for the JSDoc. Example:
-
-```ts
-/** foo does bar. */
-export function foo() {
-  // ...
-}
-```
-
-It is important that documentation is easily human-readable, but there is also a
-need to provide additional styling information to ensure generated documentation
-is more rich text. Therefore JSDoc should generally follow markdown markup to
-enrich the text.
-
-While markdown supports HTML tags, it is forbidden in JSDoc blocks.
-
-Code string literals should be braced with the back-tick (\`) instead of quotes.
-For example:
-
-```ts
-/** Import something from the `foundation` module. */
-```
-
-Do not document function arguments unless they are non-obvious of their intent
-(though if they are non-obvious intent, the API should be considered anyways).
-Therefore `@param` should generally not be used. If `@param` is used, it should
-not include the `type` as TypeScript is already strongly-typed.
-
-```ts
-/**
- * Function with non-obvious param.
- * @param foo Description of non-obvious parameter.
- */
-```
-
-Vertical spacing should be minimized whenever possible. Therefore, single-line
-comments should be written as:
-
-```ts
-/** This is a good single-line JSDoc. */
-```
-
-And not:
-
-```ts
-/**
- * This is a bad single-line JSDoc.
- */
-```
-
-Code examples should utilize markdown format, like so:
-
-````ts
-/** A straightforward comment and an example:
- * ```ts
- * import { foo } from "foundation.js";
- * foo("bar");
- * ```
- */
-````
-
-Code examples should not contain additional comments and must not be indented.
-It is already inside a comment. If it needs further comments, it is not a good
-example.
-
-#### Resolve linting problems using directives
-
-Currently, the building process uses `eslint` to lint the code. If the task
-requires code that is non-conformant to linter use `eslint-disable-next-line
-<code>` directive to suppress the warning.
-
-```typescript
-/** Constructor type for defining `LitElement` mixins. */
-// eslint-disable-next-line  @typescript-eslint/no-explicit-any
-export type LitElementConstructor = new (...args: any[]) => LitElement;
-```
-
-This ensures the continuous integration process doesn't fail due to linting
-problems, but it should be used scarcely.
-
-#### Each module should come with a test module.
-
-Every module with public functionality `foo.ts` should come with a test module
-`foo.spec.ts`. This file should be a sibling to the tested module.
-
-#### Top-level functions should not use arrow syntax.
-
-Top-level functions should use the `function` keyword. Arrow syntax should be
-limited to closures.
-
-Bad:
-
-```ts
-export const foo = (): string => {
-  return 'bar';
-};
-```
-
-Good:
-
-```ts
-export function foo(): string {
-  return 'bar';
-}
-```
-
-#### Prefer `#` over `private`
-
-We prefer the private fields (`#`) syntax over `private` keyword of TypeScript
-in the standard modules codebase. The private fields make the properties and
-methods private even at runtime. On the other hand, `private` keyword of
-TypeScript guarantee it private only at compile time and the fields are publicly
-accessible at runtime.
-
-Good:
-
-```ts
-class MyClass {
-  #foo = 1;
-  #bar() {}
-}
-```
-
-Bad:
-
-```ts
-class MyClass {
-  private foo = 1;
-  private bar() {}
-}
-```

package/commitlint.config.js

@@ -1 +0,0 @@
-export default { extends: ['@commitlint/config-conventional'] };