Files

Release v1.0.2 - Fix Buffer polyfill race condition in prompt

- Fix race condition where permission prompts failed on first request
  due to Buffer polyfill not being initialized during module evaluation
- Replace Buffer.from() with native browser APIs (atob + TextDecoder)
  in prompt.ts for reliable base64 decoding
- Add debug logging to reckless mode approval checks
- Update permission encryption to support v2 vault key format
- Enhance LoggerService with warn/error/debug methods and log storage
- Add logs component for viewing extension activity
- Simplify deriving modal component
- Rename icon files from gooti to plebian-signer
- Update permissions component with improved styling

Files modified:
- projects/chrome/src/prompt.ts
- projects/firefox/src/prompt.ts
- projects/*/src/background-common.ts
- projects/common/src/lib/services/logger/logger.service.ts
- projects/*/src/app/components/home/logs/ (new)
- projects/*/public/*.svg, *.png (renamed)

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

2025-12-20 08:52:44 +01:00

src

Release v1.0.2 - Fix Buffer polyfill race condition in prompt

2025-12-20 08:52:44 +01:00

eslint.config.js

first chrome implementation

2025-02-01 23:23:37 +01:00

ng-package.json

first chrome implementation

2025-02-01 23:23:37 +01:00

package.json

first chrome implementation

2025-02-01 23:23:37 +01:00

README.md

first chrome implementation

2025-02-01 23:23:37 +01:00

tsconfig.lib.json

Add NIP-65 relay list display and improve identity UI

2025-12-17 15:21:57 +01:00

tsconfig.lib.prod.json

first chrome implementation

2025-02-01 23:23:37 +01:00

tsconfig.spec.json

first chrome implementation

2025-02-01 23:23:37 +01:00

README.md

Common

This project was generated using Angular CLI version 19.0.0.

Code scaffolding

Angular CLI includes powerful code scaffolding tools. To generate a new component, run:

ng generate component component-name

For a complete list of available schematics (such as components, directives, or pipes), run:

ng generate --help

Building

To build the library, run:

ng build common

This command will compile your project, and the build artifacts will be placed in the dist/ directory.

Publishing the Library

Once the project is built, you can publish your library by following these steps:

Navigate to the dist directory:
```
cd dist/common
```
Run the npm publish command to publish your library to the npm registry:
```
npm publish
```

Running unit tests

To execute unit tests with the Karma test runner, use the following command:

ng test

Running end-to-end tests

For end-to-end (e2e) testing, run:

ng e2e

Angular CLI does not come with an end-to-end testing framework by default. You can choose one that suits your needs.

Additional Resources

For more information on using the Angular CLI, including detailed command references, visit the Angular CLI Overview and Command Reference page.