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.

Sign up for GitHub

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

Jump to bottom

Use Deno.execPath where possible #548

Merged
merged 1 commit into from
Jul 29, 2019
Merged

Use Deno.execPath where possible #548

merged 1 commit into from
Jul 29, 2019

Conversation

kt3k
Copy link
Member

@kt3k kt3k commented Jul 29, 2019

This is convenient when you want to test deno_std with a special build of deno.

ry
ry approved these changes Jul 29, 2019
View reviewed changes
Copy link
Member

@ry ry left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ry ry merged commit 287b0a9 into denoland:master Jul 29, 2019
@kt3k kt3k deleted the feature/deno-exec-path branch July 29, 2019 08:50
ry pushed a commit to ry/deno that referenced this pull request Oct 9, 2019
@kt3k @ry
refactor: use Deno.execPath where possible (denoland/std#548)
b76007d 
Original: denoland/std@287b0a9
inverted-capital pushed a commit to dreamcatcher-tech/napps that referenced this pull request Oct 24, 2024
@iuioiua
refactor: tweak <NotificationsList /> design (denoland#548)
7bfbf4b 
Closes denoland#467

Before:
![localhost_8000_notifications
(1)](https://github.com/denoland/saaskit/assets/29347852/7fca7708-60e1-4aec-a221-c01ffd756ccc)

After:

![localhost_8000_notifications](https://github.com/denoland/saaskit/assets/29347852/0ca4056d-e514-4c4b-9f95-a5af1cb9bcae)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@ry ry ry approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@kt3k @ry