feedback
action-automatic-release
| feedback | action-automatic-release | |
|---|---|---|
| 10 | 1 | |
| 138 | 0 | |
| 2.2% | - | |
| 1.8 | 5.5 | |
| 5 months ago | 30 days ago | |
| TypeScript | ||
| Creative Commons Attribution 4.0 | 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.
feedback
-
'everything' blocks devs from removing their own NPM packages
no-one-left-behind[1] was not even a year ago, and yet the link on npm[2] explaining why it was removed is already broken. Classic JS ecosystem.
1: https://github.com/npm/feedback/discussions/858
2: https://www.npmjs.com/package/no-one-left-behind
- Termux and nvm
-
Better npm search proposal
I created a new discussion in the npm/feedback repo to share my idea. I also mentioned my idea in relevant discussions: npm scores, Weird search behavior with stats, and Improve search functionality on npmjs.com.
-
Badge on NPM packages to show support for ES modules
We encourage you to open a discussion if you have suggestions for how we can improve npm. You don't need to have a solution to the problem you are facing to kick off a discussion. We are hoping to foster productive and collaborative conversations, so please check out how to give good feedback if you want some guidance on how to kick off a successful discussion.
-
Popular 'coa' NPM library hijacked to steal user passwords
There is an ongoing discussion about 2FA and possible bandaids for this sort of problem in the npm community forum: https://github.com/npm/feedback/discussions/588
- [Question] Response timeouts for packages with package-lock file
-
Dependency issues/warnings with setting up Gatsby + Tailwind
See - https://github.com/npm/feedback/discussions/191
-
Choosing the right runtime matters
Now there have been some discussions around to mitigate these things which might have gone side ways like https://npm.community/t/blacklist-entire-packages/9659/4 and https://github.com/npm/feedback/discussions/272. Of course there might be tools which you can use, such as running a commercial npm registry in proxy mode with blacklisting support. But what are the basic features you have as a developer that can be use to mitigate these things ?
-
Cannot Add Angular Material, can you tell me what this means?
This is likely the issue as npm 7 auto installs peer dependencies, which will fail on conflicting dependents.
action-automatic-release
-
A new public beta of GitHub Releases: How we’re improving the release experience
> If you are automating releases with GitHub Actions, we have an API that you can use in your workflows to integrate the new Automated Release Notes feature right into your existing actions pipeline.
I can't seem to find the documentation about integrating this with Actions
But I am excited to finally be able to stop maintaining my custom auto-release-changelogs action https://github.com/Trinovantes/action-automatic-release
What are some alternatives?
Data-Science-For-Beginners - 10 Weeks, 20 Lessons, Data Science for All!
okd - The self-managing, auto-upgrading, Kubernetes distribution for everyone
rfcs - Public change requests/proposals & ideation
ESLint - Find and fix problems in your JavaScript code.
Covenant - Covenant is a collaborative .NET C2 framework for red teamers.
awesome-haskell-sponsorship - 💝 Haskell profiles to sponsor
copilot.vim - Neovim plugin for GitHub Copilot
typometer - Text / code editor typing latency analyzer
cargo-crev - A cryptographically verifiable code review system for the cargo (Rust) package manager.
QuestDB - An open source time-series database for fast ingest and SQL queries
crates.io - The Rust package registry
MEMZ - A trojan made for Danooct1's User Made Malware Series.