docs: Add guidance for running tests with proper permissions#152
Merged
jaypatrick merged 2 commits intomasterfrom Jan 14, 2026
Merged
docs: Add guidance for running tests with proper permissions#152jaypatrick merged 2 commits intomasterfrom
jaypatrick merged 2 commits intomasterfrom
Conversation
- Add note that deno task test should be used instead of bare deno test - Explain required permissions (--allow-read, --allow-write, --allow-net, --allow-env, --unstable-kv) - Update example for running specific test files to include permissions This helps developers avoid permission errors when running tests directly. Co-Authored-By: Warp <agent@warp.dev>
|
Version bumped: |
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
adblock-compiler | 24493b0 | Jan 14 2026, 04:41 AM |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Developers running
deno testdirectly encounter permission errors because the tests require specific Deno permissions (--allow-read,--allow-write,--allow-net,--allow-env,--unstable-kv) that are configured in thedeno.jsontask.Solution
Added clear documentation to the README explaining:
deno task testinstead of baredeno testChanges
Testing
Verified that the documentation is clear and the examples are correct.
Co-Authored-By: Warp agent@warp.dev