deno-lambda
license-checker
Our great sponsors
deno-lambda | license-checker | |
---|---|---|
7 | 10 | |
842 | 1,572 | |
2.9% | - | |
6.7 | 0.0 | |
12 days ago | 3 months ago | |
TypeScript | JavaScript | |
MIT License | GNU General Public License v3.0 or later |
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.
deno-lambda
-
Enhancing AWS Lambda Security with Deno
Using Deno with AWS Lambda functions requires a custom runtime. You can build your own runtime or use one that already exists. If you’re concerned about security, I suggest maintaining a copy of an existing runtime and carefully inspecting updates or creating your own runtime. For this proof of concept, I deployed the Serverless Application Repository (SAR) app for Deno into my AWS account. I used the included Lambda layer and the provided.al2 Lambda runtime to create my Deno Lambda function. I created a file called index.ts with some basic JavaScript code that makes requests to two different websites and returns the HTTP status code of the response or a caught error. I then updated the function’s configuration to reference the exported handler function.
-
Deploying to Lambda with the custom layer, but brand new to Deno - how do I cache the AWS SDK? Is there a version packaged with the custom layer?
I'm doing a simple PoC / testing with Deno using https://github.com/hayd/deno-lambda and specifically the CDK instructions.
-
Big Changes Ahead for Deno
As I had mentioned, it requires using a Lambda Layer. See: https://github.com/hayd/deno-lambda/blob/2d90756a0f18b57f16e...
Using your own image (i.e. without using the base AWS image with the layer) you'd get even worse cold start times.
-
First Look at Lambda Powertools TypeScript
Decorators and TypeScript aren't supported out of the box in Lambda (without using deno) so we'll also need a transpilation step if we go this route. Fortunately this is a mostly solved problem for AWS CDK, AWS SAM and Serverless Framework users. If you want or need to roll your own, esbuild is a great place to start and seems to be the bundler of choice for this purpose.
-
Is there an easy way to deploy Deno to production like for example Node to AWS Elastic Beanstalk? Or something in the works? I want to use deno in production on AWS Amazon.
In addition to the stuff posted here, there's the deno-lambda project for deploying to AWS Lambda
-
What is missing in Deno?
Cloud hosting support. Deno runs fine in a container, but lambda/cloud function support is difficult on most providers. deno-lambda exists but it only applies to AWS and can't be used with all CICD tools. Deno Deploy also exists but it's pretty new.
license-checker
-
Consultant Asking About NPM Software Licenses
I thought that was a fairly weird question. A couple of our APIs run on Ubuntu, which contains GNU software. He has access to our source code, and I had also previously sent him the output of license checker so he really should have been able to answer this himself.
-
A developer-friendly introduction to open source licenses
NPM License Checker
-
Big Changes Ahead for Deno
I don't care whether it's all in one file or in a dozen files, but I want all of that information to be available programmatically in a text file (unlike in a readme or on Github) in a standardized location in a project.
In that respect, package.json is a strict win. Your lack of willingness to use `git blame` to see why you added a line, or lack of reasonable git comments, is not to be blamed on the file.
Complexity is unavoidable. How could you write a tool like license-checker [1] for a Go-based project without having license information in a standardized location? Without the scripts section, how can you create a tool like husky [2] that automatically installs git hooks for a project? Every single part of package.json is there for a good reason; at best you could argue that putting some of it in other files would be aesthetically superior, but that's just bikeshedding.
Complexity isn't de facto bad. Some complexity is required if you want a certain level of functionality to become available. Deno (and Go) are slowly accumulating that "cruft" as people realize that those functions are actually useful or even critical to a mature ecosystem.
[1] https://www.npmjs.com/package/license-checker
[2] https://www.npmjs.com/package/husky
-
Richard Stallman calls for software package systems that help maintain your freedoms
Yes, all npm packages are supposed to have a valid SPDX license identifier, and there is an easy way to recursively check these values
-
Introducing sbomx.com - Software Bill of Materials X
For JavaScript I always used davglass/license-checker as a starting point but it's not being maintained anymore. Then I did similar things for the backend code, put everything together and sent it to the legal and security teams. At some point I thought "There must be a better way!". So, I started building sbomx about one and a half years ago. It's working fine enough to show it to the world and gather some feedback.
-
automatically pull licenses from package.json and put them into a spreadsheet??
Check this package https://www.npmjs.com/package/license-checker
-
Italian Courts Find Open Source Software Terms Enforceable
Good doctors and drivers make mistakes, too, and they still face liability for those mistakes.
I think that if your company is large enough, you should have employees, or pay someone, to mirror your dependencies and automate license checks. There are projects that do the latter already[1][2]. You can loop your lawyers in if licenses change to ensure you don't violate them. If (A)GPL code still ships in proprietary products, that's a process problem that the company needs to solve.
[1] https://github.com/dhatim/python-license-check
[2] https://github.com/davglass/license-checker
-
Node.js Packages and Resources
license-checker - Check licenses of your app's dependencies.
-
Home Screen Shortcuts in React Native (with Expo)
If you don't know what licenses you're currently using, I suggest the license-checker NPM tool.
-
How do I explain the concept of open source software to my boss?
Also, your IT dept is not entirely without concern here, you should be ensuring that you're not violating any open source licenses in your project, and be using something like https://www.npmjs.com/package/license-checker or an equivalent license checking service in your project language to ensure that everything is kosher
What are some alternatives?
bun - Incredibly fast JavaScript runtime, bundler, test runner, and package manager – all in one
python-license-check - Check python packages from requirement.txt and report issues
powertools-lambda-typescript - Powertools is a developer toolkit to implement Serverless best practices and increase developer velocity.
npm-name - Check whether a package or organization name is available on npm
deploy_feedback - For reporting issues with Deno Deploy
npm-home - Open the npm page, Yarn page, or GitHub repo of a package
aws-embedded-metrics-node - Amazon CloudWatch Embedded Metric Format Client Library
alex - Catch insensitive, inconsiderate writing
middy - 🛵 The stylish Node.js middleware engine for AWS Lambda 🛵
Babel (Formerly 6to5) - 🐠 Babel is a compiler for writing next generation JavaScript.
aws-xray-sdk-node - The official AWS X-Ray SDK for Node.js.
np - A better `npm publish`