npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@onecx/create-workspace

v9.0.0

Published

This library was generated with [Nx](https://nx.dev).

Readme

onecx-create-workspace

This library was generated with Nx.

Creating a workspace

npx @onecx/create-workspace <flavor> <product> [--appPrefix=<prefix>]

Flavors: angular, ngrx, standalone-ngrx, react. The positional product still names the workspace directory. Creation is non-interactive.

The optional appPrefix defaults to the empty string. Both --appPrefix=acme and --appPrefix acme are supported. Pass an explicit empty string with --appPrefix="" or --appPrefix ""; empty values are forwarded to the preset. Use lowercase kebab-case without a trailing separator (for example acme-corp).

npx @onecx/create-workspace ngrx orders                    # orders-ui / orders-bff
npx @onecx/create-workspace ngrx orders --appPrefix=""     # orders-ui / orders-bff
npx @onecx/create-workspace ngrx orders --appPrefix=onecx  # onecx-orders-ui / onecx-orders-bff
npx @onecx/create-workspace react orders --appPrefix=acme  # acme-orders-ui / acme-orders-bff

The same option is available directly on the Angular, NgRx, standalone NgRx and React generators and both presets, for example:

nx g @onecx/angular-generator:ngrx orders --appPrefix=acme --non-interactive
nx g @onecx/react-generator:react orders --appPrefix="" --non-interactive

The prefix is applied once to the normalized product slug; names supplied by users are never stripped of an existing onecx- segment. Package/project/chart and operator microservice identities use <prefix-><product>-ui. Build output and Docker COPY use dist/<application-identity>/; Docker, development proxy and OpenAPI use the matching <prefix-><product>-bff:8080 hostname.

Federation remote names use camelCase (for example acmeOrdersUi), exposed modules use PascalCase plus Module (./AcmeOrdersUiModule), and web-component tags use <application-identity>-component. Angular remote module filenames use <application-identity>.remote.module.ts. Copy the matching identifiers from generated Helm values when registering the application in OneCX.

Routes and product registration are independent of appPrefix: Angular keeps its product-based /mfe/<product>/ route (the existing camelCase Helm route behavior is unchanged), while React retains onecx-<product> product registration, /onecx-<product> product base path and /mfe/onecx-<product>/ asset base. Framework packages, APIs, sharing scopes and OneCX branding are unchanged.

Building

Run nx build create-workspace to build the library.

Running unit tests

Run nx test create-workspace to execute the unit tests via Jest.