estevanmaito · hperchec · Dec 15, 2022 · Dec 15, 2022 · Dec 15, 2022 · Dec 15, 2022
diff --git a/.env b/.env
@@ -0,0 +1,4 @@
+NODE_ENV=development
+
+# CLI specific environement variables
+CLI_ENV=private
diff --git a/.env.example b/.env.example
@@ -0,0 +1,4 @@
+NODE_ENV=development
+
+# CLI specific environement variables
+CLI_ENV=private
diff --git a/.eslintignore b/.eslintignore
diff --git a/.eslintrc.json b/.eslintrc.json
diff --git a/.gitignore b/.gitignore
@@ -1,5 +1,30 @@
 node_modules
-coverage
+
+# Distribution files
 dist
+
+# local env files
+.env*
+!.env.example
+
+# Example built files
 examples/**/style.css
-examples/**/tailwind.output.css
+examples/**/tailwind.output.css
+
+# Tests
+tests/unit/.coverage
+
+# Log files
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+pnpm-debug.log*
+
+# Editor directories and files
+.idea
+.vscode
+*.suo
+*.ntvs*
+*.njsproj
+*.sln
+*.sw?
diff --git a/.prettierrc b/.prettierrc
diff --git a/.travis.yml b/.travis.yml
@@ -3,18 +3,17 @@ cache: npm
 notifications:
   email: false
 node_js:
-  - 12
-  - 14
+  - 18
   - node
 install:
   - npm install
 script:
   - npm run lint
   - npm run test:coverage
   - npm run build
-after_success:
-  - npm run codecov
-  - npm run semantic-release
+# after_success:
+#   - npm run codecov
+#   - npm run semantic-release
 branches:
   only:
     - master
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -0,0 +1,37 @@
+# Changelog
+
+## <small>2.0.1 (2025-05-05)</small>
+
+* build: remove old external dep ([8079133](https://github.com/hperchec/tailwindcss-multi-theme/commit/8079133))
+* build: update package.json files field ([9376920](https://github.com/hperchec/tailwindcss-multi-theme/commit/9376920))
+* docs: update readme template ([6fcb7e0](https://github.com/hperchec/tailwindcss-multi-theme/commit/6fcb7e0))
+
+## 2.0.0 (2025-05-05)
+
+* build: add @release-it/conventional-changelog dependency ([8c4294f](https://github.com/hperchec/tailwindcss-multi-theme/commit/8c4294f))
+* build: migrate from webpack to vite ([acf99d6](https://github.com/hperchec/tailwindcss-multi-theme/commit/acf99d6))
+* build: migrate to eslint v9 and use @stylistic rules ([af7a40e](https://github.com/hperchec/tailwindcss-multi-theme/commit/af7a40e))
+* build: remove useless files ([a552beb](https://github.com/hperchec/tailwindcss-multi-theme/commit/a552beb))
+* build: replace husky and commitizen by juisy features ([88004f2](https://github.com/hperchec/tailwindcss-multi-theme/commit/88004f2))
+* build: update .gitignore file ([828f9b7](https://github.com/hperchec/tailwindcss-multi-theme/commit/828f9b7))
+* build: update eslint config ([d896ad3](https://github.com/hperchec/tailwindcss-multi-theme/commit/d896ad3))
+* build: update package-lock.json ([daf47a2](https://github.com/hperchec/tailwindcss-multi-theme/commit/daf47a2))
+* build: update package-lock.json ([91d94ed](https://github.com/hperchec/tailwindcss-multi-theme/commit/91d94ed))
+* build: update release config ([2615a07](https://github.com/hperchec/tailwindcss-multi-theme/commit/2615a07))
+* build: update release config ([010ee18](https://github.com/hperchec/tailwindcss-multi-theme/commit/010ee18))
+* build: update release config ([bbc7a83](https://github.com/hperchec/tailwindcss-multi-theme/commit/bbc7a83))
+* build: use juisy library ([f54e382](https://github.com/hperchec/tailwindcss-multi-theme/commit/f54e382))
+* build: use master branch instead of main in release config ([dc81ecf](https://github.com/hperchec/tailwindcss-multi-theme/commit/dc81ecf))
+* test: migrate to vitest and rewrite tests ([3e17a47](https://github.com/hperchec/tailwindcss-multi-theme/commit/3e17a47))
+* test: remove console.log ([0daeaa2](https://github.com/hperchec/tailwindcss-multi-theme/commit/0daeaa2))
+* style: lint files ([c965451](https://github.com/hperchec/tailwindcss-multi-theme/commit/c965451))
+* docs: update contributing ([aee56b5](https://github.com/hperchec/tailwindcss-multi-theme/commit/aee56b5))
+* docs: update docs ([fbdfbcc](https://github.com/hperchec/tailwindcss-multi-theme/commit/fbdfbcc))
+* docs: update docs and licence ([8411b8b](https://github.com/hperchec/tailwindcss-multi-theme/commit/8411b8b))
+* docs: update simple example ([8dca335](https://github.com/hperchec/tailwindcss-multi-theme/commit/8dca335))
+* ci: update .travis.yml ([db00188](https://github.com/hperchec/tailwindcss-multi-theme/commit/db00188))
+* chore: remove postcss-selector-parser dependency ([96fb3df](https://github.com/hperchec/tailwindcss-multi-theme/commit/96fb3df))
+* chore: update plugin ([58b966e](https://github.com/hperchec/tailwindcss-multi-theme/commit/58b966e))
+* chore: update simple example ([49c9e79](https://github.com/hperchec/tailwindcss-multi-theme/commit/49c9e79))
+* feat: rewrite code in TypeScript and use new tailwind v3 plugin API ([1f6003f](https://github.com/hperchec/tailwindcss-multi-theme/commit/1f6003f))
+* wip: migrate to tailwindcss v3 ([a505af1](https://github.com/hperchec/tailwindcss-multi-theme/commit/a505af1))
diff --git a/COMMIT_CONVENTION.md b/COMMIT_CONVENTION.md
@@ -0,0 +1,116 @@
+# Commit Message Format
+
+> ❗ IMPORTANT
+>
+> This documentation is based on Angular [commit message guidelines](https://github.com/angular/angular/blob/main/contributing-docs/commit-message-guidelines.md)
+
+We have very precise rules over how our Git commit messages must be formatted.
+This format leads to **easier to read commit history** and makes it analyzable for changelog generation.
+
+Each commit message consists of a **header**, a **body**, and a **footer**.
+
+```
+<header>
+<BLANK LINE>
+<body>
+<BLANK LINE>
+<footer>
+```
+
+The `header` is mandatory and must conform to the [Commit Message Header](#commit-header) format.
+
+The `body` is mandatory for all commits except for those of type "docs".
+When the body is present it must be at least 20 characters long and must conform to the [Commit Message Body](#commit-body) format.
+
+The `footer` is optional. The [Commit Message Footer](#commit-footer) format describes what the footer is used for and the structure it must have.
+
+## Commit Message Header
+
+```
+<type>(<scope>): <short summary>
+  │       │             │
+  │       │             └─⫸ Summary in present tense. Not capitalized. No period at the end.
+  │       │
+  │       └─⫸ Commit Scope: see below
+  │
+  └─⫸ Commit Type: build|ci|docs|feat|fix|perf|refactor|test
+```
+
+The `<type>` and `<summary>` fields are mandatory, the `(<scope>)` field is optional.
+
+### Type
+
+Must be one of the following:
+
+| Type         | Description                                                                                         |
+|--------------|-----------------------------------------------------------------------------------------------------|
+| **build**    | Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm) |
+| **ci**       | Changes to our CI configuration files and scripts (examples: Github Actions, SauceLabs)             |
+| **docs**     | Documentation only changes                                                                          |
+| **feat**     | A new feature                                                                                       |
+| **fix**      | A bug fix                                                                                           |
+| **perf**     | A code change that improves performance                                                             |
+| **refactor** | A code change that neither fixes a bug nor adds a feature                                           |
+| **test**     | Adding missing tests or correcting existing tests                                                   |
+
+### Scope
+The scope should be the name of the npm package affected (as perceived by the person reading the changelog generated from commit messages).
+
+The following is the list of supported scopes:
+
+* `scope-a`
+* `scope-b`
+* `scope-c`
+
+### Summary
+
+Use the summary field to provide a succinct description of the change:
+
+* use the imperative, present tense: "change" not "changed" nor "changes"
+* don't capitalize the first letter
+* no dot (.) at the end
+
+## Commit Message Body
+
+Just as in the summary, use the imperative, present tense: "fix" not "fixed" nor "fixes".
+
+Explain the motivation for the change in the commit message body. This commit message should explain _why_ you are making the change.
+You can include a comparison of the previous behavior with the new behavior in order to illustrate the impact of the change.
+
+## Commit Message Footer
+
+The footer can contain information about breaking changes and deprecations and is also the place to reference GitHub issues and other PRs that this commit closes or is related to.
+For example:
+
+```
+BREAKING CHANGE: <breaking change summary>
+<BLANK LINE>
+<breaking change description + migration instructions>
+<BLANK LINE>
+<BLANK LINE>
+Fixes #<issue number>
+```
+
+or
+
+```
+DEPRECATED: <what is deprecated>
+<BLANK LINE>
+<deprecation description + recommended update path>
+<BLANK LINE>
+<BLANK LINE>
+Closes #<pr number>
+```
+
+Breaking Change section should start with the phrase `BREAKING CHANGE: ` followed by a *brief* summary of the breaking change, a blank line, and a detailed description of the breaking change that also includes migration instructions.
+
+Similarly, a Deprecation section should start with `DEPRECATED: ` followed by a short description of what is deprecated, a blank line, and a detailed description of the deprecation that also mentions the recommended update path.
+
+## Revert commits
+
+If the commit reverts a previous commit, it should begin with `revert: `, followed by the header of the reverted commit.
+
+The content of the commit message body should contain:
+
+- information about the SHA of the commit being reverted in the following format: `This reverts commit <SHA>`,
+- a clear description of the reason for reverting the commit message.
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -0,0 +1,78 @@
+# Contribution guide
+
+First, please check the [code of conduct](./CODE_OF_CONDUCT.md)
+
+## Commits
+
+Commit messages are linted with `commitlint` in the `commit-msg` git hook, following the **angular** convention. Please check the [commit convention](./COMMIT_CONVENTION.md).
+
+## Build
+
+The distribution code is built with [Vite](https://v5.vite.dev/guide/) (v5). You can check the [configuration file](./vite.config.ts).
+
+To build, run the following command:
+
+```sh
+npm run build
+```
+
+## Tests
+
+### Units
+
+To run unit tests, run the following command:
+
+```sh
+npm run test
+# With coverage enabled
+npm run test:coverage
+# Watch mode
+npm run test:watch
+# With @vitest/ui
+npm run test:ui
+```
+
+### Examples
+
+There are example folders to test usage cases.
+
+In an example folder (eg: `./examples/simple`), run the following commands:
+
+```sh
+# Install dependencies
+npm install
+# Build source code
+npm build
+```
+
+Then, you can open the `index.html` in your browser.
+
+## Releases
+
+Run the following command to make a release:
+
+```sh
+# Show help
+npm run release --help
+# Release a patch
+npm run release --increment patch
+# Release a specific version
+npm run release -i 2.0.0
+# To increment the current prerelease. For example:
+# from   1.0.0-beta.1
+# to     1.0.0-beta.2
+npm run release -i pre
+```
+
+> 💡 See also:
+>
+> - the **juisy** [release tool documentation](<%= __JUISY_DOCS_HOMEPAGE__ %>)
+> - the **release-it** [package documentation](https://github.com/release-it/release-it)
+
+## Documentation
+
+Run the following command to generate project documentation:
+
+```sh
+npm run docs
+```
diff --git a/LICENSE b/LICENSE
@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2020 Estevan Maito
+Copyright (c) 2025 Estevan Maito & Hervé Perchec
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal