Merge pull request #20 from MODSetter/dev

feat: MonoRepo

Author: MODSetter

.gitmodules

@@ -214,7 +214,7 @@ After filling in your SurfSense API key you should be able to use extension now.
 ---
  ### **FrontEnd**
 
--  **Next.js 15.2.0**: React framework featuring App Router, server components, automatic code-splitting, and optimized rendering.
+-  **Next.js 15.2.3**: React framework featuring App Router, server components, automatic code-splitting, and optimized rendering.
 
 -  **React 19.0.0**: JavaScript library for building user interfaces.
 

README.md

@@ -0,0 +1,2 @@
+PLASMO_PUBLIC_API_SECRET_KEY = "surfsense"
+PLASMO_PUBLIC_BACKEND_URL = "http://127.0.0.1:8000"

ss-cross-browser-extension

@@ -0,0 +1,34 @@
+# name: "Submit to Web Store"
+# on:
+#   workflow_dispatch:
+
+# jobs:
+#   build:
+#     runs-on: ubuntu-latest
+#     steps:
+#       - uses: actions/checkout@v3
+#       - name: Cache pnpm modules
+#         uses: actions/cache@v3
+#         with:
+#           path: ~/.pnpm-store
+#           key: ${{ runner.os }}-${{ hashFiles('**/pnpm-lock.yaml') }}
+#           restore-keys: |
+#             ${{ runner.os }}-
+#       - uses: pnpm/action-setup@v2.2.4
+#         with:
+#           version: latest
+#           run_install: true
+#       - name: Use Node.js 16.x
+#         uses: actions/setup-node@v3.4.1
+#         with:
+#           node-version: 16.x
+#           cache: "pnpm"
+#       - name: Build the extension
+#         run: pnpm build
+#       - name: Package the extension into a zip artifact
+#         run: pnpm package
+#       - name: Browser Platform Publish
+#         uses: PlasmoHQ/bpp@v3
+#         with:
+#           keys: ${{ secrets.SUBMIT_KEYS }}
+#           artifact: build/chrome-mv3-prod.zip

surfsense_browser_extension/.env.example

@@ -0,0 +1,35 @@
+
+# See https://help.github.com/articles/ignoring-files/ for more about ignoring files.
+
+# dependencies
+/node_modules
+/.pnp
+.pnp.js
+
+# testing
+/coverage
+
+# misc
+.DS_Store
+*.pem
+
+# debug
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+.pnpm-debug.log*
+
+# local env files
+.env*.local
+
+out/
+build/
+dist/
+
+# plasmo
+.plasmo
+
+# typescript
+.tsbuildinfo
+
+/trash

surfsense_browser_extension/.github/workflows/submityml

@@ -0,0 +1,26 @@
+/**
+ * @type {import('prettier').Options}
+ */
+export default {
+  printWidth: 80,
+  tabWidth: 2,
+  useTabs: false,
+  semi: false,
+  singleQuote: false,
+  trailingComma: "none",
+  bracketSpacing: true,
+  bracketSameLine: true,
+  plugins: ["@ianvs/prettier-plugin-sort-imports"],
+  importOrder: [
+    "<BUILTIN_MODULES>", // Node.js built-in modules
+    "<THIRD_PARTY_MODULES>", // Imports not matched by other special words or groups.
+    "", // Empty line
+    "^@plasmo/(.*)$",
+    "",
+    "^@plasmohq/(.*)$",
+    "",
+    "^~(.*)$",
+    "",
+    "^[./]"
+  ]
+}

surfsense_browser_extension/.gitignore

@@ -0,0 +1,37 @@
+# SurfSense Cross Browser Extension
+
+Use this guide to build for your browser https://docs.plasmo.com/framework/workflows/build
+
+This is a [Plasmo extension](https://docs.plasmo.com/) project bootstrapped with [`plasmo init`](https://www.npmjs.com/package/plasmo).
+
+## Getting Started
+
+First, run the development server:
+
+```bash
+pnpm dev
+# or
+npm run dev
+```
+
+Open your browser and load the appropriate development build. For example, if you are developing for the chrome browser, using manifest v3, use: `build/chrome-mv3-dev`.
+
+You can start editing the popup by modifying `popup.tsx`. It should auto-update as you make changes. To add an options page, simply add a `options.tsx` file to the root of the project, with a react component default exported. Likewise to add a content page, add a `content.ts` file to the root of the project, importing some module and do some logic, then reload the extension on your browser.
+
+For further guidance, [visit our Documentation](https://docs.plasmo.com/)
+
+## Making production build
+
+Run the following:
+
+```bash
+pnpm build
+# or
+npm run build
+```
+
+This should create a production bundle for your extension, ready to be zipped and published to the stores.
+
+## Submit to the webstores
+
+The easiest way to deploy your Plasmo extension is to use the built-in [bpp](https://bpp.browser.market) GitHub action. Prior to using this action however, make sure to build your extension and upload the first version to the store to establish the basic credentials. Then, simply follow [this setup instruction](https://docs.plasmo.com/framework/workflows/submit) and you should be on your way for automated submission!