PSPDFKit / PSPDFKit/nutrient-web-examples
📦 Request: Example project using @nutrient/pspdfkit with Angular frontend inside Electron app
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 89
- Forks
- 3
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 5
Description
I’m currently using @nutrient/pspdfkit and I would really appreciate a working example showing how to integrate it in an Angular-based frontend running inside an Electron app.
Project structure
My setup is split into two parts:
• Root project: has Electron-related code, its own package.json, and handles launching the Electron app.
• application/ subfolder: contains the Angular app with its own package.json, CLI config, etc.
Electron either:
• loads the Angular app from localhost:4200 during development
• or points to the Angular build output (dist/) in production.
What I need
I’d love an example project or starter showing:
• How to properly include and configure @nutrient/pspdfkit in this kind of architecture
• Recommended way to load and display a PDF using the library inside an Angular component
• Handling of .mjs modules, if needed
• Any gotchas or Electron-specific requirements (e.g. sandbox, nodeIntegration, preload scripts)
Thanks in advance for your time and this great library!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the root and application/ package.json files and the Angular CLI configuration, then examine how Electron loads localhost:4200 in development and dist/ in production. A working example should configure @nutrient/pspdfkit, display a PDF from an Angular component, and document any .mjs, sandbox, nodeIntegration, or preload requirements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, electron
- Domain
- desktop, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100