Skip to content
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

Generate Invoice PDF #1835

Merged
merged 30 commits into from
Jan 8, 2025
Merged

Generate Invoice PDF #1835

merged 30 commits into from
Jan 8, 2025

Conversation

steven-tey
Copy link
Collaborator

@steven-tey steven-tey commented Dec 24, 2024

Caveat: Turbopack doesn't play nice with react-pdf so we need to disable --turbo flag for the pnpm dev script for this to work

This pull request introduces several changes to enhance the billing and invoicing functionalities. The changes mainly focus on generating and managing invoice prefixes, creating detailed invoice PDFs, and updating the schema to support unique invoice numbers.

Enhancements to Billing and Invoicing:

Schema and Utility Updates:

Dependency Additions:

Copy link

vercel bot commented Dec 24, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
dub ✅ Ready (Inspect) Visit Preview Jan 8, 2025 10:01pm

Copy link

socket-security bot commented Dec 24, 2024

New dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/@react-pdf/renderer@4.1.5 environment, filesystem Transitive: eval, network, unsafe +54 18.2 MB diegomura
npm/react-pdf-tailwind@2.3.0 Transitive: environment, eval, filesystem, network, unsafe +61 25.1 MB aanckar

View full report↗︎

Copy link

socket-security bot commented Jan 6, 2025

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert Package NoteSourceCI
Obfuscated code npm/@react-pdf/pdfkit@3.2.0 ⚠︎

View full report↗︎

Next steps

What is obfuscated code?

Obfuscated files are intentionally packed to hide their behavior. This could be a sign of malware.

Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

  • @SocketSecurity ignore npm/@react-pdf/pdfkit@3.2.0

@steven-tey steven-tey merged commit d589117 into main Jan 8, 2025
4 of 5 checks passed
@steven-tey steven-tey deleted the pdf branch January 8, 2025 21:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants