
Security News
Another Round of TEA Protocol Spam Floods npm, But It’s Not a Worm
Recent coverage mislabels the latest TEA protocol spam as a worm. Here’s what’s actually happening.
@mrgrain/jsii-struct-builder
Advanced tools
Build jsii structs with ease.
Jsii doesn't support TypeScript Utility Types like Partial or Omit, making it difficult to re-use existing struct interfaces.
With this package, you can work around that limitation and create brand new struct interfaces based on the jsii specification of any existing structs, their parents, and your custom specification.
From jsii's perspective, these structs are completely new types. From a maintainer's perspective, they require the same minimal effort as utility types do. Everybody wins!
Install with:
npm install --save-dev @mrgrain/jsii-struct-builder
Use the jsii FQN to mix in an existing struct.
Use omit to remove any properties you are not interested in.
new ProjenStruct(project, { name: 'MyProjectOptions'})
.mixin(Struct.fromFqn('projen.typescript.TypeScriptProjectOptions'))
.omit('sampleCode', 'projenrcTs', 'projenrcTsOptions');
New properties can be added with a @jsii/spec definition.
Complex types can be used and will be imported using their FQN.
Any existing properties of the same name will be replaced.
new ProjenStruct(project, { name: 'MyProjectOptions'})
.mixin(Struct.fromFqn('projen.typescript.TypeScriptProjectOptions'))
.add(
{
name: 'booleanSetting',
type: { primitive: jsii.PrimitiveType.Boolean }
},
{
name: 'complexSetting',
type: { fqn: "my_project.SomeEnum" }
}
);
Existing properties can be updated.
The provided partial @jsii/spec definition will be deep merged with the existing spec.
Updates can be also be used to rename properties.
new ProjenStruct(project, { name: 'MyProjectOptions'})
.mixin(Struct.fromFqn('projen.typescript.TypeScriptProjectOptions'))
.update('typescriptVersion', { optional: false })
.update('sampleCode', {
docs: {
summary: 'New summary',
default: 'false',
}
}
)
.update('eslint', { name: 'linter' });
Struct and ProjenStruct both share the same interface.
This allows some advanced applications.
For example you can manipulate the source for re-use:
const base = Struct.fromFqn('projen.typescript.TypeScriptProjectOptions');
base.omit('sampleCode', 'projenrcTs', 'projenrcTsOptions');
Or you can mix on ProjenStruct with another:
const foo = new ProjenStruct(project, { name: 'Foo'})
const bar = new ProjenStruct(project, { name: 'Bar'})
bar.mixin(foo);
The default configuration makes assumptions about the new interface that are usually okay.
For more complex scenarios fqn, filePath and importLocations can be used to influence the rendered output.
new JsiiInterface(project, {
name: 'MyProjectOptions',
fqn: 'my_project.nested.location.MyProjectOptions',
filePath: 'src/nested/my-project-options.ts',
importLocations: {
'my_project': '../enums'
}
})
.add({
name: 'complexSetting',
type: { fqn: "my_project.SomeEnum" }
});
FAQs
Build jsii structs with ease
We found that @mrgrain/jsii-struct-builder demonstrated a healthy version release cadence and project activity because the last version was released less than 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
Recent coverage mislabels the latest TEA protocol spam as a worm. Here’s what’s actually happening.

Security News
PyPI adds Trusted Publishing support for GitLab Self-Managed as adoption reaches 25% of uploads

Research
/Security News
A malicious Chrome extension posing as an Ethereum wallet steals seed phrases by encoding them into Sui transactions, enabling full wallet takeover.