A powerful and lightweight inversion of control container for JavaScript & Node.js apps powered by TypeScript.
-
Updated
Oct 8, 2020 - TypeScript
{{ message }}
A powerful and lightweight inversion of control container for JavaScript & Node.js apps powered by TypeScript.
Jodd! Lightweight. Java. Zero dependencies. Use what you like.
Powerful dependency injection for iOS & OSX (Objective-C & Swift)
Dependency Injection Framework for Unity3D
The dependency injection container for humans
Your first K.I.S.S Unity 3D Framework.
Extremely powerful Inversion of Control (IoC) container for Node.JS
Lightweight dependency injection container for JavaScript/TypeScript
A delightful way to building a RESTful API with NodeJs & TypeScript by @w3tecch
This repository contains development environment for the entire package
We could add the following rules (https://github.com/sbousseaden/YaraHunts) to the default Yara rules available
For the hacktoberfest and to prepare the v6, you can easily find typo on this branch/PR:
https://github.com/TypedProject/tsed/pull/941/files
If you find typo, create branch from https://github.com/TypedProject/tsed/tree/v6-update-documentation, then create PR on
this branch. I'll merge it quickly :)
A curated list of awesome YARA rules, tools, and people.
Signature base for my scanner tools
Dependency injection framework for Python
建议BaseRepository 里增加返回 IQueryable 的Get / GetAsync 的方法
有了之后就可以在service 里面进行拼接LINQ 用于获取到ViewModel中关联其他类的数据
基于 IoC 的 Go 后端一站式开发框架
Most .py files use #!/usr/bin/python3 as shebang, but few others use #!/usr/bin/env python3.
Files which use #!/usr/bin/env python3:
./contrib/eventdb/common.py
./intelmq/bin/intelmq_generate_misp_objects_templates.py
./intelmq/tests/bots/parsers/github_feed/test_parser.py
These files should use #!/usr/bin/python3 for the sake of consistency.
A collection of sources of indicators of compromise.
Add a description, image, and links to the ioc topic page so that developers can more easily learn about it.
To associate your repository with the ioc topic, visit your repo's landing page and select "manage topics."
Starting from version 12.12.0, Node.js offers built-in support for translating error stack traces using source maps - learn more here: https://medium.com/@nodejs/source-maps-in-node-js-482872b56116
Let's rework
@loopback/buildto use this new feature on recent version of Node.js, instead ofsource-map-supportmodule.If it's possible, then implement a fallback to npm module `source-map-s