-
-
Notifications
You must be signed in to change notification settings - Fork 5
Feature/bun runtime #45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…T strategy tests refactor: update fetch mock to use global as any in song webhook service tests fix: return ArrayBuffer instead of Buffer in file service
…e and browser environments
…d updating type references
… client configuration
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi! Was the removal of the assets folder from src necessary? Be sure it doesn't break loading of the font/note block sprite when generating the thumbnail server-side :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I moved the assets folder outside the src directory to better align with common project structures where static or shared resources are separated from the application code logic, similar to how the public folder is treated in frontend and backend projects. This helps keep the source code focused and makes asset management more centralized and intuitive.
I’ve ensured that all paths referencing fonts and the note block sprite used in thumbnail generation are updated accordingly.
…sController tests
…ve mock implementations
… jest.spyOn with spyOn
…d improve error handling
… .eslintrc.js with .eslintrc.json
This pull request introduces significant changes to the project, including a migration from
pnpm/nodetobun, enhancements to build and runtime configurations, and various codebase improvements.Migration to
bun:package.jsonscripts to usebuninstead ofpnpmfor tasks such as development, building, and testing. Addedconcurrentlyto run the backend and frontend simultaneously for development.Production build:
For running in production with
bun, the following command is used:Nest backend
This will build the NestJS backend for production.
This will start the NestJS production build.
Next frontend
This will build the Next.js frontend for production.
This will start the Next.js production build.