Security News
vlt Debuts New JavaScript Package Manager and Serverless Registry at NodeConf EU
vlt introduced its new package manager and a serverless registry this week, innovating in a space where npm has stagnated.
Use experimental decorators with zero runtime cost and without increasing your bundle size.
decky strives for full compatiblity with TypeScript, Prettier, and the rest of the JavaScript ecosystem.
decky
is an esbuild plugin.
npm install decky
In your esbuild configuration:
const { build } = require("esbuild");
const { load } = require("decky");
build({
// ...rest of your esbuild config
plugins: [await load()];
})
The GraphQLSchema.decorator
example lets you write GraphQL types inline with zero runtime overhead:
import { auto, field, type } from "./GraphQLSchema.decorator";
@type("Person")
export class Person {
@field("ID", "user id number")
id: number;
@auto
username: string;
@field("number")
signUpTimestamp: number;
}
At build-time, it outputs the GraphQL schema to a file:
type Person {
signUpTimestamp: number
username: string
# user id number
id: ID
}
To the bundler, there are no decorators. Zero-runtime.
export class Person {
id: number;
username: string;
signUpTimestamp: number;
}
What if we wanted JSON Schema instead of GraphQL? Well, if the interface is the same but you had a JSONSchema.decorator
:
+import { auto, field, type } from "./GraphQLSchema.decorator";
-import { auto, field, type } from "./JSONSchema.decorator";
@type("Person")
export class Person {
// ...rest of file
You'd get this instead:
{
"Person": {
"signUpTimestamp": {
"type": "number"
},
"username": {
"type": "string"
},
"id": {
"type": "number",
"description": "user id number"
}
}
}
Decorators are run at build-time. This uses a handcrafted bespoke not-JavaScript AST. The syntax looks like decorators enough to fool TypeScript's type checker, but under the hood, its entirely different.
Decorator imports are removed during tree-shaking, leaving no trace.
By default, files that write new decorators need to end in any of these extensions:
.decorator.ts
.decky.ts
.dec.ts
And it needs to export decorators
which is an object where the key
is the function name and the value is the decorator function (property
, propertyVoid
or klass
).
With no arguments:
import { propertyVoid } from "decky";
// void means the decorator accepts no arguments from the code calling it
export const debugOnly = propertyVoid(() => {
if (!process.env.DEBUG) {
return "";
}
});
export const decorators = { debugOnly };
You use it like this:
import { debugOnly } from "./debugOnly.decorator";
export class Task {
@debugOnly
shouldLog = true;
run() {
// ... code in here
}
}
Then, when !DEBUG
, Task is compiled as:
export class Task {
run() {
// ... code in here
}
}
What we return in property
or propertyVoid
replaces from the @
to the next two lines. If we don't return anything or return undefined
, it just deletes the line containing the @ symbol.
You can use decky to edit code at build-time or for generating metadata for code.
TODO example
FAQs
Use experimental decorators with zero runtime overhead.
The npm package decky receives a total of 6 weekly downloads. As such, decky popularity was classified as not popular.
We found that decky demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
vlt introduced its new package manager and a serverless registry this week, innovating in a space where npm has stagnated.
Security News
Research
The Socket Research Team uncovered a malicious Python package typosquatting the popular 'fabric' SSH library, silently exfiltrating AWS credentials from unsuspecting developers.
Security News
At its inaugural meeting, the JSR Working Group outlined plans for an open governance model and a roadmap to enhance JavaScript package management.