Bunshi 2.0

.devcontainer/devcontainer.json

@@ -0,0 +1,38 @@
+// For format details, see https://aka.ms/devcontainer.json. For config options, see the
+// README at: https://github.com/devcontainers/templates/tree/main/src/alpine
+{
+	"name": "Alpine",
+	// Or use a Dockerfile or Docker Compose file. More info: https://containers.dev/guide/dockerfile
+	"image": "mcr.microsoft.com/devcontainers/base:alpine-3.18",
+	"features": {
+		"ghcr.io/devcontainers/features/node:1": {}
+	},
+	"customizations": {
+		"vscode": {
+			"extensions": [
+				"astro-build.astro-vscode",
+				"Vue.volar",
+				"GitHub.codespaces",
+				"GitHub.vscode-pull-request-github",
+				"github.vscode-github-actions",
+				"esbenp.prettier-vscode",
+				"ZixuanChen.vitest-explorer"
+			]
+		}
+	}
+
+	// Features to add to the dev container. More info: https://containers.dev/features.
+	// "features": {},
+
+	// Use 'forwardPorts' to make a list of ports inside the container available locally.
+	// "forwardPorts": [],
+
+	// Use 'postCreateCommand' to run commands after the container is created.
+	// "postCreateCommand": "uname -a",
+
+	// Configure tool-specific properties.
+	// "customizations": {},
+
+	// Uncomment to connect as root instead. More info: https://aka.ms/dev-containers-non-root.
+	// "remoteUser": "root"
+}

.github/workflows/main.yml

@@ -22,8 +22,11 @@ jobs:
       - name: Install deps and build (with cache)
         uses: bahmutov/npm-install@v1
 
-      - name: Test
-        run: npm test -- --ci --coverage --maxWorkers=2
+      - name: Test (vitest)
+        run: npm run test:code
 
       - name: Build
         run: npm run build
+
+      - name: Size Test
+        run: npm run test:size

.github/workflows/website.yml

@@ -0,0 +1,39 @@
+name: Deploy to GitHub Pages
+
+on:
+  # Trigger the workflow every time you push to the `main` branch
+  # Using a different branch name? Replace `main` with your branch’s name
+  push:
+    branches: [ main ]
+  # Allows you to run this workflow manually from the Actions tab on GitHub.
+  workflow_dispatch:
+
+# Allow this job to clone the repo and create a page deployment
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout your repository using git
+        uses: actions/checkout@v3
+      - name: Install, build, and upload your site
+        uses: withastro/action@v0
+        with:
+            path: website # The root location of your Astro project inside the repository. (optional)
+            # node-version: 16 # The specific version of Node that should be used to build your site. Defaults to 16. (optional)
+            # package-manager: yarn # The Node package manager that should be used to install dependencies and build your site. Automatically detected based on your lockfile. (optional)
+
+  deploy:
+    needs: build
+    runs-on: ubuntu-latest
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    steps:
+      - name: Deploy to GitHub Pages
+        id: deployment
+        uses: actions/deploy-pages@v1

.gitignore

@@ -3,3 +3,4 @@
 node_modules
 .cache
 dist
+coverage

.vscode/settings.json

@@ -0,0 +1,3 @@
+{
+    "astro.language-server.ls-path": ""
+}

CHANGELOG.md

@@ -7,6 +7,46 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [2.0.0] - 2023-09-20
+
+Bunshi 2.0 is the next big release of `jotai-molecules`. We were working on adding `vue` support, and in the process realized that not only did
+we not rely on any code from `jotai`, but also that the concept of dependency injection for the frontend that we were working on was actually
+useful for a number of different tools and libraries.
+
+For `vue` we realized that molecules are a useful way of sharing and scoping a `ref` across an application. This is similar to the goals of `pinia`,
+but we could accomplish it in a more granular way without relying on strings keys.
+
+We also saw that other tools like `valtio` suffer from the need for memoization. Valtio recommends using `useRef` for keeping a stable proxy scoped to
+a component or a component tree.
+
+So, instead of creating `vue-molecules` and `valtio-molecules` and others, we decided to keep it simple and rename our library.
+
+The new name for `jotai-molecules` is Bunshi. bunshi (分子, ぶんし) is the japanese word for molecule. Why bunshi? We are big fans of `valtio`, `zustand` and `jotai`, 
+so we wanted to keep with the tradition of naming libraries using other languages. If you didn't now, `zustand` is German for "state" and `valtio` is Finnish for "state".
+
+The other thing that is releasing at the same time here is our new documentation website. It's difficult to keep everything up to date in a single Readme, so we moved to a static site generator.
+
+Moving for `jotai-molecules` to `bunshi`? To migrate change your imports from `jotai-molecules` to `bunshi/react` for example:
+
+```diff
+- import { useMolecule, molecule } from "jotai-molecules"
++ import { useMolecule, molecule } from "bunshi/react"
+```
+
+### Changed
+- Renamed from `jotai-molecules` to `bunshi`
+- Default export no longer returns react. Users will need to change imports from `jotai-molecules` to `bunshi/react`
+
+### Added
+- `bunshi` Vanilla JS support
+- `bunshi/vue` Vue support
+- `bunshi/react` React-specific import
+- `createInjector` and `getDefaultInjector` to access internal state
+- `moleculeInterface` for creating bindable interfaces
+- `ComponentScope` for pushing state down into components
+- Documentation website
+
+
 ## [1.1.1] - 2023-04-20
 
 ### Changed
@@ -40,7 +80,8 @@ Initial release of `jotai-molecules`
 - `createScope` for creating a scope for molecules
 - `ScopeProvider` a React component for providing scope to the tree
 
-[unreleased]: https://github.com/saasquatch/jotai-molecules/compare/v1.1.1...HEAD
+[unreleased]: https://github.com/saasquatch/jotai-molecules/compare/v2.0.0...HEAD
+[2.0.0]: https://github.com/saasquatch/jotai-molecules/releases/tag/v2.0.0
 [1.1.1]: https://github.com/saasquatch/jotai-molecules/releases/tag/v1.1.1
 [1.1.0]: https://github.com/saasquatch/jotai-molecules/releases/tag/v1.1.0
 [1.0.3]: https://github.com/saasquatch/jotai-molecules/releases/tag/v1.0.3

CONTRIBUTING.md

@@ -2,7 +2,7 @@
 
 ## Reporting Issues
 
-If you have found what you think is a bug, please [file an issue](https://github.com/saasquatch/jotai-molecules/issues/new).
+If you have found what you think is a bug, please [file an issue](https://github.com/saasquatch/bunshi/issues/new).
 
 ## Suggesting new features