openinf / openinf-util-errors Goto Github PK
View Code? Open in Web Editor NEWEssential utility errors inspired by Node.js core error codes
Home Page: https://github.com/OpenINF/openinf-util-errors#readme
License: Other
Essential utility errors inspired by Node.js core error codes
Home Page: https://github.com/OpenINF/openinf-util-errors#readme
License: Other
Explicit types where they can be easily inferred may add unnecessary verbosity for variables or parameters initialized to a number, string, or boolean
There are 3 occurrences of this issue in the repository.
See all occurrences on DeepSource → deepsource.io/gh/openinf/util-errors/issue/JS-0331/occurrences/
This package is currently being flagged by Socket with a Severity: Medium issue due to a lack of tests. This is negatively impacting how its quality score is performing over there. I do not yet have a testing strategy in mind, but we should ensure that our tests are at least in line with any usage guidelines we provide to ensure that results are consistent. There are a lot of ways to wrongly check an error (e.g., instanceof
is not cross-realm). Those antipattern ways should probably not be what we use in our tests since they are not very consistent and may give folks the wrong impression who refer to tests for usage examples.
We are being suggested to add tests and publish a new version of the package once we have done so. It is unclear whether the tests are expected to be runnable using what we have specified in dependencies
or whether devDependencies
would be sufficient. I want to avoid shipping packages that contain devDependencies
since they frequently become outdated a lot more quickly than everything else, meaning that we would have to ship much more often. Seeing as how it would be for a reason that doesn't affect the APIs provided by the module, it would be giving consumers very little reason to upgrade to these newer versions only having these innocuous dependency updates that have no effect on production code.
Add the “hacktoberfest” topic to your repository to opt-in to Hacktoberfest and indicate you’re looking for contributions.
Apply the “hacktoberfest” label to issues you want contributors to help within your GitHub or GitLab project.
Add a CONTRIBUTING.md
file with contribution guidelines to your repository.
Choose issues that have a well-defined scope and are self-contained.
Adopt a code of conduct to create a greater sense of inclusion and community for contributors.
Be ready to review pull/merge requests, accepting those that are valid by merging them, leaving an overall approving review, or by adding the “hacktoberfest-accepted” label.
Reject any spammy requests you receive by labeling them as “spam”, and any other invalid contributions by closing them or labeling them as “invalid”.
This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.
These updates have all been created already. Click a checkbox below to force a retry/rebase of any.
.github/workflows/codeql-analysis.yml
actions/checkout v3
github/codeql-action v2
github/codeql-action v2
github/codeql-action v2
.github/workflows/semgrep.yml
actions/checkout v3
ubuntu 20.04
package.json
@types/node 20.x.x
typescript 5.1.3
pnpm 8.6.3
.nvmrc
node 20
Comparing to null
without a type-checking operator (===
or !==
), can have unintended results as the comparison will evaluate to true
when comparing to not just a null
, but also an undefined
value.
There are 2 occurrences of this issue in the repository.
See all occurrences on DeepSource → deepsource.io/gh/openinf/util-errors/issue/JS-0059/occurrences/
It is preferable not to check the compiled typescript into our repo — let's remove that javascript from here. Additionally, we should use babel for this transpilation instead of the typescript compiler. We will, however, continue using tsc
for type checking and type definition generation.
DeepScan has been configured to check for ESLint config instead of using its default rules. This means that it will be ready for us once ESLint is good to go here.
You've analyzed the project with ESLint, but the ESLint analysis failed by the ESLint error.
After checking the details of error and configuring ESLint correctly, please reanalyze this project.
ESLint couldn't find a configuration file. To set up a configuration file for this project, please run:
eslint --init
According to the Internationalization Best Practices for Spec Developers published by W3C Internationalization Working Group, we should be providing language-independent identifiers for errors.
It seems like the code
property on each of our error instances would be the most appropriate place for this, but we are currently using constant-case identifiers (e.g., ERR_MISSING_OPTION
like Node.js core) for this. Depending on how these errors are being checked at run-time, and if we want to be able to maintain interop with Node.js in the future, it may be worthwhile to use a different property for the language-independent identifier, which will most likely be composed strictly of digits.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.