
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.
@2sic.com/dnn-sxc-angular
Advanced tools
Connect DNN / DotNetNuke and 2sxc to Angular 6-11 and probably newer as well
End of Life
Important: This is end of life. It is replaced by sxc-angular which is for Angular 13+ and supports Dnn and Oqtane.
This is a connector for angular 6-11+ (git | web) for developers using
This connector...
data.query$ to get data with little effort from the serverIt uses observables to make it happen, thereby avoiding timing / async problems common in this scenario.
Best watch the introduction video and read the general docs.
It's published on npm, so the most common way is to get it using npm with
npm i "@2sic.com/dnn-sxc-angular" --save. But we recommend that you follow the quick-start guide.
This will now work automatically, because all headers etc. are now automatically added by the system. So just use your normal http-requests and everything works like magic 😊
By default dnn-sxc-angular will pick up all the values on the page automatically by asking $2sxc for the initial values. Yet there are some things that $2sxc doesn't know, or why you may want to override.
dnn-sxc-angular will check for some properties on the <app-root> tag to see if it should do something special. If not found, it will default to the most common value.
edition would tell angular that it's running in an app-edition where multiple editions exist. So it would use live etc. for it base path. Default is empty/not set.api-edition is important to access another edition of the API. default is empty/not setangular-path (new in 11.01)Once installed correctly, the context is autoloaded when the AppComponent which inherits DnnAppComponent does the super(...) call - like this:
export class AppComponent extends DnnAppComponent {
constructor(el: ElementRef, context: Context) {
super(el, context);
}
}
If you want to provide alternate configurations, you can do this here, by changing the super call. Here's an example (you can do more, check the code):
export class AppComponent extends DnnAppComponent {
constructor(el: ElementRef, context: Context) {
super(el, context.preConfigure({moduleId: 42}));
}
}
This package is fully documented with intellisense. Once configured it ensures that all HTTP requests in angular include DNN headers. It also contains a Data and Api object, which provides 3 observable streams
data.content$<T>(contentTypeName)data.query$<T>(queryName)api.get$<T>(apiNameAndParams)api.post$<T>(apiNameAndParams)To use them, best check out the tutorial app or simply work through TypeScript intelisense - we documented all the commands.
angular-path to use as base for lazy loadingThese are things the 2sxc developers plan on enhancing
context.sxc... classic JS APIcontext.sxc... classic JS APIFAQs
Connect DNN / DotNetNuke and 2sxc to Angular 6-11 and probably newer as well
We found that @2sic.com/dnn-sxc-angular demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 3 open source maintainers 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.