Used pathlib for everything basically. Now it returns the files in a table format based on what the user chose for example: size/date/name, also can choose if you want them descending or ascending

Changelog

• It works well. It prints the files in a directory based on size/date/name and descending or ascending.
• Started making the project, discovered lots of things.
• Initial commit.
• first commit

Something is coming…

I started making a new CLI tool, since I really like python to make stuff. This CLI tool will scan a certain directory provided by the user and then returns the files based on what filter the user choice

• Size filter
• Newest to oldest filter
• Oldest to newest filter

Changelog

• Started making the project, discovered lots of things.
• Initial commit.
• first commit

Changelog

• Added Chrome Web Store link to landing page.
• Fixed minor system prompt issue
• Replaced URL in Chrome Extension
• Made a backend-worker directory for Cloudflare Workers since Render doesn’t work well.

Changelog

• Bug Fixes: Made an options page so the user can set/re-set the API key and also made it so you can’t continue, if the API key input is empty.
• Update README.md
• Finished project: v0.1.0

I forgot to push the changes before requesting re-certification. :(

Changelog

• Fixed the manifest.json unnecessary permissions and added a privacy policy page for Chrome Web Store.
• Update README to simplify backend instructions
• Change backend requirement to optional in README
• Fixed a deployment bug being caused by a component prop.
• Fixed some visual bugs and a mistake in the backend URL.
• Removed mobile-nav.tsx as it was not being used and was causing deployment bugs.
• Made a new and improved landing page.
• Made a dropdown selector to select the prompt framework.
• Delete .vscode directory
• Fixed some logo issues

P.S: This isn’t vibecoded (to all the people saying it is), the landing page was made using pre-made blocks from this website. And I forgot to devlog 4 hours of work =)

The Project Has Been Shipped!

You can now calculate how many cookies you need for every item in the store!

Tweaked the UI a little bit so it looks better, added Goal functionality, soon store functionaity will be added so the user can browse the flavortown store within the extension and choose what to track instead of manually typing in name and cookie amount, that will still be there and optional.

So basically the extension prompts the user to enter the API key which they can get from their settings page and then input it, which then fetched the cookies and username and displays them.

Finished project, i’ll review it again before shipping.

First Devlog (The project is actually finished this is just required for shipping)

SaveIt has been shipped! 🚀🔥

I know this project has no devlogs, but this is because it was a small project. Essentially what the chrome extension does, is it takes a URL provided by the user with a filename that the user gets to decide and downloads it. Right now it’s only available through the github repository but soon it’ll be available throught the Chrome Web Store.

Started working a bit on the actual chat functionality using Groq’s API.

Worked quite a bit on the chat page, made it as a protected route, fixed login functionality and sign out functionality. Refined the UI a little bit and started working on the logic part so the chats actually get saved.

Started making the UI of the chat page. (Sidebar, AI Prompt)
It is mobile responsive aswell.

I worked on transfering some parts of the design from the old front end to the new Next.js front end.

I worked on getting my Nest.js backend with Prisma ORM connected with my Neon Postgres DB. A couple of things left to go, such as adding Clerk for auth.