-
Notifications
You must be signed in to change notification settings - Fork 3
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
🧑💻 Migrate to Deno for development #279
Conversation
Signed-off-by: Dmitriy Lazarev <w@kich.dev>
Signed-off-by: Dmitriy Lazarev <w@kich.dev>
Signed-off-by: Dmitriy Lazarev <w@kich.dev>
Signed-off-by: Dmitriy Lazarev <w@kich.dev>
Signed-off-by: Dmitriy Lazarev <w@kich.dev>
Signed-off-by: Dmitriy Lazarev <w@kich.dev>
Signed-off-by: Dmitriy Lazarev <w@kich.dev>
✅ Deploy Preview for interactors canceled.
|
Package Changes Through 430a678No changes. Add a change file through the GitHub UI by following this link. Read about change files or the docs at github.com/jbolda/covector |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking lovely! Just a few comments on the package.json
which we should check in every file / package.
ce955d4
to
df3c773
Compare
df3c773
to
430a678
Compare
@@ -8,7 +8,7 @@ | |||
"repository": "https://github.com/thefrontside/interactors.git", | |||
"homepage": "https://frontside.com/interactors", | |||
"author": "Frontside Engineering <engineering@frontside.com>", | |||
"license": "MIT", | |||
n "license": "MIT", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems it's typo
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nooooooooo! 😬
Motivation
There are two main reasons that we want to migrate to Deno:
Approach
Migrate to a single Deno workspace, and then use covector for change management and publication. Releases will represented via a tag, and then publication to package registries can happen independently.
Shout out to @wKich for doing the heavy lifting on this!