@iarunsaragadam/ngx-tailwind-flex-ui 0.0.1-canary.0.0

package/.editorconfig

@@ -0,0 +1,13 @@
+# Editor configuration, see http://editorconfig.org
+root = true
+
+[*]
+charset = utf-8
+indent_style = space
+indent_size = 2
+insert_final_newline = true
+trim_trailing_whitespace = true
+
+[*.md]
+max_line_length = off
+trim_trailing_whitespace = false

package/.github/workflows/ci.yml

@@ -0,0 +1,131 @@
+name: CI & Release
+
+on:
+  push:
+    branches:
+      - main
+    tags:
+      - "v*"
+  pull_request:
+    branches:
+      - main
+
+permissions:
+  contents: write
+  packages: write
+
+jobs:
+  commit-lint:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - name: Lint Commit Messages
+        uses: wagoid/commitlint-github-action@v5
+
+  build-test:
+    runs-on: ubuntu-latest
+    needs: commit-lint
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 20
+          registry-url: "https://registry.npmjs.org/"
+          cache: "npm"
+      - run: npm ci --legacy-peer-deps
+      - run: npx playwright install --with-deps
+      - run: npx nx affected -t lint test build e2e
+
+  canary-release:
+    if: github.event_name == 'push' && github.ref == 'refs/heads/main'
+    needs: build-test
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 20
+          registry-url: "https://registry.npmjs.org/"
+      - run: npm ci --legacy-peer-deps
+      - name: Publish Canary Release
+        env:
+          GITHUB_TOKEN: ${{ secrets.GH_TOKEN }}
+          NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+        run: npx semantic-release --branches main --tag-format "canary-\${version}"
+
+  tagged-release:
+    if: github.event_name == 'push' && startsWith(github.ref, 'refs/tags/v')
+    needs: build-test
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 20
+          registry-url: "https://registry.npmjs.org/"
+      - run: npm ci --legacy-peer-deps
+      - name: Determine Release Type
+        id: release_type
+        run: |
+          TAG_NAME="${GITHUB_REF#refs/tags/}"
+          if [[ "$TAG_NAME" == *"-beta"* ]]; then
+            echo "release_type=beta" >> $GITHUB_ENV
+          elif [[ "$TAG_NAME" == *"-rc"* ]]; then
+            echo "release_type=rc" >> $GITHUB_ENV
+          else
+            echo "release_type=latest" >> $GITHUB_ENV
+          fi
+
+      - name: Publish Tagged Release
+        env:
+          GITHUB_TOKEN: ${{ secrets.GH_TOKEN }}
+          NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+        run: npx semantic-release --branches main --tag ${{ env.release_type }}
+
+  label-prs:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - name: Auto-label PRs
+        uses: actions/labeler@v5
+        with:
+          repo-token: "${{ secrets.GH_TOKEN }}"
+
+  dependabot-auto-merge:
+    needs: [build-test]
+    runs-on: ubuntu-latest
+    steps:
+      - name: Auto-merge Dependabot PRs
+        uses: fastify/github-action-merge-dependabot@v3
+        with:
+          github-token: ${{ secrets.GH_TOKEN }}
+          target: minor
+
+  deploy-storybook:
+    needs: build-test
+    if: github.ref == 'refs/heads/main'
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 20
+          cache: "npm"
+      - run: npm ci --legacy-peer-deps
+      - name: Build Storybook
+        run: npx nx run ngx-tailwind-flex-ui:build-storybook
+      - name: Deploy Storybook to GitHub Pages
+        uses: peaceiris/actions-gh-pages@v3
+        with:
+          github_token: ${{ secrets.GH_TOKEN }}
+          publish_dir: dist/storybook/ngx-tailwind-flex-ui

package/.prettierignore

@@ -0,0 +1,6 @@
+# Add files here to ignore them from prettier formatting
+/dist
+/coverage
+/.nx/cache
+/.nx/workspace-data
+.angular

package/.prettierrc

@@ -0,0 +1,3 @@
+{
+  "singleQuote": true
+}

package/.vscode/extensions.json

@@ -0,0 +1,9 @@
+{
+  "recommendations": [
+    "nrwl.angular-console",
+    "esbenp.prettier-vscode",
+    "dbaeumer.vscode-eslint",
+    "firsttris.vscode-jest-runner",
+    "ms-playwright.playwright"
+  ]
+}

package/CODE_OF_CONDUCT.md

@@ -0,0 +1,130 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our  
+project and our community a harassment-free experience for everyone, regardless  
+of age, body size, visible or invisible disability, ethnicity, sex  
+characteristics, gender identity and expression, level of experience,  
+education, socio-economic status, nationality, personal appearance, race,  
+caste, color, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,  
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our  
+community include:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes,  
+  and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the overall  
+  community
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery, and sexual attention or advances of  
+  any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others’ private information, such as a physical or email address,  
+  without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a  
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of  
+acceptable behavior and will take appropriate and fair corrective action in  
+response to any behavior that they deem inappropriate, threatening, offensive,  
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject  
+comments, commits, code, wiki edits, issues, and other contributions that are  
+not aligned to this Code of Conduct, and will communicate reasons for moderation  
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when  
+an individual is officially representing the community in public spaces.  
+Examples of representing our community include using an official e-mail address,  
+posting via an official social media account, or acting as an appointed  
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be  
+reported by contacting the maintainers. Reporting options will be updated in  
+future versions of this project.
+
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the  
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining  
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed  
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing  
+clarity around the nature of the violation and an explanation of why the  
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of  
+actions.
+
+**Consequence**: A warning with consequences for continued behavior. No  
+interaction with the people involved, including unsolicited interaction with  
+those enforcing the Code of Conduct, for a specified period of time. This  
+includes avoiding interactions in community spaces as well as external channels  
+like social media. Violating these terms may lead to a temporary or permanent  
+ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including  
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public  
+communication with the community for a specified period of time. No public or  
+private interaction with the people involved, including unsolicited interaction  
+with those enforcing the Code of Conduct, is allowed during this period.  
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community  
+standards, including sustained inappropriate behavior, harassment of an  
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the  
+community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],  
+version 2.1, available at  
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html](https://www.contributor-covenant.org/version/2/1/code_of_conduct.html).
+
+Community Impact Guidelines were inspired by  
+[Mozilla’s code of conduct enforcement ladder](https://github.com/mozilla/diversity).
+
+For answers to common questions about this code of conduct, see the FAQ at  
+[https://www.contributor-covenant.org/faq](https://www.contributor-covenant.org/faq).  
+Translations are available at  
+[https://www.contributor-covenant.org/translations](https://www.contributor-covenant.org/translations).
+
+[homepage]: https://www.contributor-covenant.org

package/CONTRIBUTING.md

@@ -0,0 +1,145 @@
+# Contributing to ngx-tailwind-flex-ui 🚀
+
+Thank you for considering contributing to this project! Your help is **greatly appreciated**.  
+This guide will help you contribute effectively.
+
+---
+
+## 🛠️ How to Contribute
+
+### 1️⃣ Fork & Clone the Repository
+You **cannot push directly to this repository**.  
+Instead, you must **fork the repository** and work in your own copy.
+
+#### **Step 1: Fork the Repository**
+1. Go to the **ngx-tailwind-flex-ui** repository on GitHub:  
+   👉 [https://github.com/iarunsaragadam/ngx-tailwind-flex-ui](https://github.com/iarunsaragadam/ngx-tailwind-flex-ui)
+2. Click the **Fork** button (top-right corner).
+3. This creates **your own copy** of the project under `your-username/ngx-tailwind-flex-ui`.
+
+#### **Step 2: Clone Your Fork Locally**
+Once forked, open your terminal and run:
+```sh
+git clone https://github.com/YOUR_USERNAME/ngx-tailwind-flex-ui.git
+cd ngx-tailwind-flex-ui
+```
+
+#### **Step 3: Set Up the Main Repository as an Upstream**
+To keep your fork updated, connect it to the original repository:
+```sh
+git remote add upstream https://github.com/iarunsaragadam/ngx-tailwind-flex-ui.git
+git fetch upstream
+```
+
+---
+
+### 2️⃣ Follow Branching Strategy
+This project follows **Trunk-Based Development**:
+
+| Branch  | Purpose |
+|---------|---------|
+| `main`  | Always stable, deployable at all times |
+| (Feature flags) | Features are merged into `main` behind flags |
+
+All new contributions should be made in a **separate branch in your fork**.
+
+---
+
+### 3️⃣ Create a New Branch for Your Work
+Before making any changes, **always create a new branch** inside your fork.
+
+#### **Step 1: Create a Branch**
+Run the following command (replace `feature-branch` with a meaningful name):
+```sh
+git checkout -b feature-branch
+```
+
+#### **Step 2: Make Your Changes**
+- Edit the code, add new features, or fix bugs.
+- Save your files.
+
+#### **Step 3: Stage and Commit Your Changes**
+Run:
+```sh
+git add .
+git commit -m "feat: add new feature"
+```
+
+💡 **Follow the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) format** to ensure correct versioning.
+
+---
+
+### 4️⃣ Run Tests & Linting Before Pushing
+Before submitting your changes, ensure they pass all checks:
+```sh
+npm run lint
+npm run test
+npm run build
+```
+⚠️ **If any test fails, CI will reject your PR. Fix issues before pushing!**
+
+---
+
+## 🔀 Creating a Pull Request (PR)
+
+### ✅ **PR Checklist**
+Before submitting a PR:
+- [ ] **Ensure tests pass** (`npm run test`).
+- [ ] **Write meaningful commit messages**.
+- [ ] **Include relevant documentation**.
+- [ ] **Target `main` branch**.
+- [ ] **Use feature flags if your feature isn’t stable yet**.
+
+### **Step-by-Step PR Flow**
+#### **Step 1: Push Your Branch to Your Fork**
+Since **all contributors must work from their fork**, you **must push your changes to your fork first**:
+```sh
+git push origin feature-branch
+```
+
+#### **Step 2: Create a Pull Request**
+1. Go to **your forked repository** on GitHub.
+2. Click the **"Compare & pull request"** button.
+3. Ensure your PR **targets**:
+   - **Base repository:** `iarunsaragadam/ngx-tailwind-flex-ui`
+   - **Base branch:** `main`
+   - **Head repository:** `your-username/ngx-tailwind-flex-ui`
+   - **Compare branch:** `feature-branch`
+4. Add a clear **PR title** and **description**.
+5. Click **"Create Pull Request"**.
+
+---
+
+### 🔄 Keeping Your Fork Updated
+Before making new contributions, **sync your fork** with the latest changes:
+
+```sh
+git checkout main
+git fetch upstream
+git merge upstream/main
+git push origin main
+```
+This ensures your fork is **up-to-date** before you create a new branch for additional contributions.
+
+---
+
+## 🚀 Automated Releases
+This project uses **Semantic Release**:
+- **Every commit to `main` triggers a `canary` release** (`@canary` on npm).
+- **Stable releases** are created based on commit messages.
+- **Changelogs & GitHub releases** are generated automatically.
+
+---
+
+## 📌 Code of Conduct
+Please follow the [Code of Conduct](./CODE_OF_CONDUCT.md).
+
+---
+
+## 🎯 Need Help?
+If you're unsure about something:
+- Open a **GitHub Issue**.
+- Ask in **Discussions**.
+- Mention a maintainer in a PR.
+
+We appreciate your contributions! ❤️🚀

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,3 @@
+# ngx-tailwind-flex-ui
+
+ngx-tailwind-flex-ui is a flexible Angular UI kit built on Tailwind CSS, offering a collection of pre-styled components that are simple to modify and theme.