![require(esm) Backported to Node.js 20, Paving the Way for ESM-Only Packages](https://cdn.sanity.io/images/cgdhsj6q/production/be8ab80c8efa5907bc341c6fefe9aa20d239d890-1600x1097.png?w=400&fit=max&auto=format)
Security News
require(esm) Backported to Node.js 20, Paving the Way for ESM-Only Packages
require(esm) backported to Node.js 20, easing the transition to ESM-only packages and reducing complexity for developers as Node 18 nears end-of-life.
@acoustic-content-sdk/app
Advanced tools
Angular schematics used to add application support for Acoustic Content.
This schematics allows to add Acoustic Content SDK support to your Angular application.
From the command line from within you application folder run
npx ng add @acoustic-content-sdk/app
This will ask for the API_URL of your Acoustic Content tenant.
The command will add the Acoustic Content SDK to your project and install the required dependencies.
An application built for Acoustic Content is delivered in two versions, a view
and an edit
version. The versions differ in the set of modules they pull in from the Acoustic Content SDK at application bootstrap time, the actual application code, i.e. the application components are identical between these versions.
The split makes sense, because the edit
version enables inline edit features for the application and this requires to pull in more dependencies than there are required for an application without edit capabilities. So the application build for edit
is larger than that for view
. It is important however to keep the application size for view
as small as possible to deliver the best application performance possible. Hence the split.
The different build versions are represented as configurations
in the angular.json
file. You can e.g. build the application in view mode for production calling ng build --configuration=production,view
or in edit mode ng build --configuration=production,edit
. The same overlay technique works for other build targets.
Home > @acoustic-content-sdk/app
Angular schematics used to add application support for Acoustic Content.
Function | Description |
---|---|
addToApplication(options) | Adds SDK support to an existing Angular application |
Variable | Description |
---|---|
VERSION | Version and build number of the package |
Home > @acoustic-content-sdk/app > addToApplication
Adds SDK support to an existing Angular application
Signature:
export declare function addToApplication(options: Schema): Rule;
Parameter | Type | Description |
---|---|---|
options | Schema | the schematics object used to describe the applicatiojn |
Returns:
Rule
the schematics rule that executes the transform
Home > @acoustic-content-sdk/app > VERSION
Version and build number of the package
Signature:
VERSION: {
version: {
major: string;
minor: string;
patch: string;
branch: string;
};
build: Date;
}
FAQs
Angular schematics used to add application support for Acoustic Content.
The npm package @acoustic-content-sdk/app receives a total of 0 weekly downloads. As such, @acoustic-content-sdk/app popularity was classified as not popular.
We found that @acoustic-content-sdk/app demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 8 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
require(esm) backported to Node.js 20, easing the transition to ESM-only packages and reducing complexity for developers as Node 18 nears end-of-life.
Security News
PyPI now supports iOS and Android wheels, making it easier for Python developers to distribute mobile packages.
Security News
Create React App is officially deprecated due to React 19 issues and lack of maintenance—developers should switch to Vite or other modern alternatives.