IPC144
execa
Our great sponsors
IPC144 | execa | |
---|---|---|
70 | 20 | |
0 | 6,349 | |
- | - | |
0.0 | 9.6 | |
over 2 years ago | 2 days ago | |
HTML | JavaScript | |
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
IPC144
-
Code review
Reviewing two PRs from a classmate is one of the duties for this project. The PRs, as well as my reviews, are available here and here. Both of the PRs I reviewed were really well-written and detailed, with very few mistakes. It was interesting to observe how different people approached certain changes, such as adding a svg file.
-
Release 0.3 Seneca-ICTOER/IPC144
For this assignment we had to contribute to a Seneca repository. I chose the IPC144 repo.
-
Result: Contributing to a open source project
Issue: https://github.com/Seneca-ICTOER/IPC144/issues/64 I worked on the standardized front matter across all markdown pages. This open-source project is the C language course notes of my major program.
-
Release 0.4 - Final
And the reason why the web-only artifacts is still appear on the PDF page is because the --excludeSelectors option is not implemented enough. I have to add .clean-btn to the --excludeSelectors, the purpose of this is not to include the "On the page" artifact in side the PDF page. This is the final source code I have implement for this improvement and my pull request
-
Release 0.4 - Release
I think I was able to do a good job meeting my goals I gave myself in my planning phase of this release. I was able to finish the issues well on schedule while balancing my other courses like I hoped and I was able to properly audit and fix both issues #122 and #123 without needing too many changes after review. What I learned from those two issues is the importance to read and checkout other issues/pull requests, especially for smaller repos. As I was told in the review for both my issues, I learned that the project recently made changes with how we would format the frontmatter. In PR #142 we no longer use the slug for pages due to inconsistency with links and we also need to include a description to follow the standardized Frontmatter as updated in PR #143.
-
Release 0.4 - My progress
The first issue I was working on IPC144 Course Note is about improving the usability of the PDF file generated from the website. All contents are generated inside the PDF, however, we want to get this better since some of the pictures are not showing properly, and also the web-only artifacts are still on the PDF, which we do not want it when we use the "PDF" version. convert-to-pdf.sh file would be modified a bit to accomplish this.
-
Release 0.4 Release
Issue #113
-
Finishing Up Release 0.4
PR
-
Release 0.4 - Part 3
As for this pull request, the code review went much more smoothly, with me having to only make minor changes to ensure that it would not cause any errors when built.
-
Release 0.4 - Part 2
2. #issue-107
execa
-
Google ZX – A tool for writing better scripts
I’m partial to Sindre Sorhus’ execa, this document outlines the differences:
https://github.com/sindresorhus/execa/blob/main/docs/scripts...
- Execa: Process Execution for Humans in Node.js
-
The Bun Shell
Yeah, or over https://github.com/sindresorhus/execa?
And given the existence of those npm packages, is there any aspect of Bun Shell that required it to be built into the Bun runtime instead of published to npm?
For something which works across all JS runtimes (Deno, Node) and achieves basically the same, check out the popular JS library Execa[1]. Works like a charm!
[1]: https://github.com/sindresorhus/execa
-
Building Reactive CLIs with Ink - React CLI library
To simplify the process of running the commands, I will use execa - abstraction library on top of Node.js child_process methods.
-
How to run DB migrations in CICD Pipeline
Hello, this is an interesting problem. At https://stacktape.com (where we're creating a developer-friendly abstraction of AWS), we're recommending 2 options: - use a "deployment script" (basically a custom-resource lambda function that runs during the CloudFormation deployment). You can install prisma into it, and then execute the migration command from the lambda function using something like execa, if you're using Javascript/Typescript. You can easily do this with Stacktape anytime. - use a bastion (EC2) instance (deployed to the the VPC where your RDS db is). The cheapest instances cost ~4.5$/month, so it shoudln't be too costly. You can also securely connect to it using EC2 instance connect, that leverages IAM to grant permissions to connect to it. (this is something we're currently implementing as Stacktape, and will be ready in ~2 weeks).
- Fluent shell scripts with JavaScript
-
Testing in ReScript
For FE, it’s usually Cypress or Playwright; for BE, it’s to run a server and start sending requests; for CLI, I like the tool called execa.
-
How to use execa@6 with NestJs?
Since version 6 execa is pure ES module. An attempt to import a package into NestJS project results in an error:
-
Getting vim ex command output without a TTY?
Essentially when I run this from my shell I get a listing of keymaps configured for vim. However, when I run it from a program without a PTY or TTY (e.g., via Rust's Command or Node's execa) I get an exit code of 0 and no output.
What are some alternatives?
IPC144 - Seneca College IPC144 Course Notes
zx - A tool for writing better scripts
telescope - A tool for tracking blogs in orbit around Seneca's open source involvement
Electron - :electron: Build cross-platform desktop apps with JavaScript, HTML, and CSS
IPC144
nodegit - Native Node bindings to Git.
Docusaurus - Easy to maintain open source documentation websites.
schemapack - Create a schema object to encode/decode your JSON in to a compact byte buffer with no overhead.
lighthouse - Automated auditing, performance metrics, and best practices for the web.
hypernova - A service for server-side rendering your JavaScript views
brain-marks - [Not Active] Open-source iOS app to save and categorize tweets
nan - Native Abstractions for Node.js