oc 0.50.47 → 0.50.49

package/AGENTS.md

@@ -1,58 +0,0 @@
-## Rules
-
-### 1. File & Folder Organization
-- **Domain-driven structure**: Organize code by business domains (`cli/`, `registry/`, `components/`, `utils/`)
-- **Subfolder patterns**: Use consistent patterns (`domain/`, `routes/`, `views/`, `middleware/`)
-- **File naming**: Use kebab-case for all files and folders (`components-cache`, `package-json-validator`)
-- **Module exports**: Use `index.ts` files for clean public APIs and re-exports
-- **Centralized types**: Place shared TypeScript interfaces in `src/types.ts`
-
-### 2. TypeScript Coding Standards
-- **Strict compilation**: All code must pass TypeScript strict mode checks
-- **Interface design**: Use comprehensive interfaces with optional properties (`?` syntax)
-- **Type imports**: Use `import type` for type-only dependencies
-- **Union types**: Use union types for constrained values (`'oc-registry' | 'oc-registry-local'`)
-- **Generic interfaces**: Extend base types like `PackageJson` for specialized interfaces
-- **Naming conventions**:
-  - camelCase for variables/functions (`componentName`, `getComponent`)
-  - PascalCase for interfaces/types (`Component`, `RegistryOptions`)
-  - UPPER_CASE for constants (`DEFAULT_PORT`)
-
-### 3. Code Style & Patterns
-- **Import organization**: Group imports (Node.js with `node:` prefix, external libraries, local modules)
-- **Function style**: Use arrow functions for simple operations, function declarations for main functions
-- **Async patterns**: Prefer async/await over Promise chains
-- **Object destructuring**: Use destructuring in function parameters
-- **Descriptive naming**: Use clear, descriptive function names (`getComponentRetrievingInfo` vs `getComp`)
-
----
-
-## File Structure Enforcement
-
-### Required Directory Structure
-```
-src/
-├── cli/
-│   ├── commands.ts
-│   ├── domain/           # Business logic
-│   ├── facade/           # Public APIs
-│   └── programmatic-api.ts
-├── registry/
-│   ├── routes/           # Express routes
-│   ├── domain/           # Business logic
-│   │   └── validators/   # Input validation
-│   ├── views/            # JSX components
-│   │   └── partials/     # Reusable components
-│   └── middleware/       # Express middleware
-├── components/           # Component implementations
-├── utils/               # Shared utilities
-├── types.ts            # Centralized type definitions
-└── resources/          # Static resources
-```
-
-### File Extension Rules
-- `.ts` for TypeScript modules and business logic
-- `.tsx` for React/JSX components and views
-- `index.ts` for module exports and public APIs
-
----

package/CONTRIBUTING.md

@@ -1,68 +0,0 @@
-# Contributing guidelines
-
-Contributes are more than welcome!
-
-## Troubleshooting
-
-If you find an issue, feel free to check the [issues](https://github.com/opencomponents/oc/issues) page, and open a new one if you need.
-
-### Sending a Pull Request
-
-If you want to send a Pull Request, ensure you join the conversation first on the [issues page](https://github.com/opencomponents/oc/issues)! This is to avoid multiple people working on the same thing. You can get in touch via the [chat](https://gitter.im/opentable/oc) too.
-
-When preparing a pull request, ensure all the tests pass locally running `npm test`. If you have write/admin access, do it on a new branch on the upstream opencomponents repo. This allows all the test to run smoothly.
-
-A couple of coding rules:
-
-- never play with git history
-- don't auto-merge
-- merge only when tests are all green
-
-### Publishing new version to npm
-
-You need to be enabled for doing this.
-
-- `master` should be all green. If not, make it green first.
-- git checkout master
-- git pull --tags
-- Run `npm run <versionType>` for new version.
-  - While on 0.X.X (not stable):
-    - `npm run publish-patch` for bugfixes, new features
-    - `npm run publish-minor` for all breaking changes
-    - `npm run publish-major` NOT YET. Still need to define milestones for 1.0.0.
-
-## Code of Conduct
-
-This Code of Conduct is adapted from [Rust's wonderful
-CoC](http://www.rust-lang.org/conduct.html).
-
-- We are committed to providing a friendly, safe and welcoming
-  environment for all, regardless of gender, sexual orientation,
-  disability, ethnicity, religion, or similar personal characteristic.
-- Please avoid using overtly sexual nicknames or other nicknames that
-  might detract from a friendly, safe and welcoming environment for
-  all.
-- Please be kind and courteous. There's no need to be mean or rude.
-- Respect that people have differences of opinion and that every
-  design or implementation choice carries a trade-off and numerous
-  costs. There is seldom a right answer.
-- Please keep unstructured critique to a minimum. If you have solid
-  ideas you want to experiment with, make a fork and see how it works.
-- We will exclude you from interaction if you insult, demean or harass
-  anyone. That is not welcome behavior. We interpret the term
-  "harassment" as including the definition in the [Citizen Code of
-  Conduct](http://citizencodeofconduct.org/); if you have any lack of
-  clarity about what might be included in that concept, please read
-  their definition. In particular, we don't tolerate behavior that
-  excludes people in socially marginalized groups.
-- Private harassment is also unacceptable. No matter who you are, if
-  you feel you have been or are being harassed or made uncomfortable
-  by a community member, please contact us at oc@opentable.com with a capture (log, photo, email) of
-  the harassment if possible. Whether you're a regular contributor or
-  a newcomer, we care about making this community a safe place for you
-  and we've got your back.
-- Likewise any spamming, trolling, flaming, baiting or other
-  attention-stealing behavior is not welcome.
-- Avoid the use of personal pronouns in code comments or
-  documentation. There is no need to address persons when explaining
-  code (e.g. "When the developer")

package/LICENSE

@@ -1,20 +0,0 @@
-Copyright (c) 2019 OpenComponents Community
-
-Permission is hereby granted, free of charge, to any person obtaining
-a copy of this software and associated documentation files (the
-"Software"), to deal in the Software without restriction, including
-without limitation the rights to use, copy, modify, merge, publish,
-distribute, sublicense, and/or sell copies of the Software, and to
-permit persons to whom the Software is furnished to do so, subject to
-the following conditions:
-
-The above copyright notice and this permission notice shall be
-included in all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
-EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
-MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
-IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
-CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
-TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
-SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

package/biome.json

@@ -1,52 +0,0 @@
-{
-	"$schema": "https://biomejs.dev/schemas/2.1.2/schema.json",
-	"vcs": {
-		"enabled": false,
-		"clientKind": "git",
-		"useIgnoreFile": false
-	},
-	"files": {
-		"ignoreUnknown": false,
-		"includes": ["preview/**/*", "src/**/*", "!src/components/oc-client/**/*"]
-	},
-	"formatter": {
-		"enabled": true,
-		"indentStyle": "tab"
-	},
-	"linter": {
-		"enabled": true,
-		"rules": {
-			"recommended": true,
-			"correctness": {
-				"useJsxKeyInIterable": "off"
-			},
-			"complexity": {
-				"useLiteralKeys": "off",
-				"noExcessiveNestedTestSuites": "off"
-			},
-			"style": {
-				"noParameterAssign": "off",
-				"noNonNullAssertion": "off",
-				"useTemplate": "off"
-			},
-			"suspicious": {
-				"noExplicitAny": "off"
-			}
-		}
-	},
-	"javascript": {
-		"formatter": {
-			"trailingCommas": "none",
-			"indentStyle": "space",
-			"quoteStyle": "single"
-		}
-	},
-	"assist": {
-		"enabled": true,
-		"actions": {
-			"source": {
-				"organizeImports": "on"
-			}
-		}
-	}
-}

package/lefthook.yml

@@ -1,5 +0,0 @@
-pre-commit:
-  commands:
-    check:
-      glob: '*.{js,ts,cjs,mjs,d.cts,d.mts,jsx,tsx}'
-      run: npx biome check --no-errors-on-unmatched --files-ignore-unknown=true {staged_files}