Start
Foundations
Design Systemv1.3.0Search documentation
Search for a command to run or a page to navigate to.
Design Systemv1.3.0Search for a command to run or a page to navigate to.
Fixes for the common install, authentication, and styling problems.
When installing @strongtie/design-system goes wrong, it is usually one of these five symptoms. Find yours below and follow the steps.
Ensure @strongtie/design-system/styles is imported in your entry file.
Styles must come before component usage.
Clear the build cache and restart the dev server.
Verify your Azure DevOps PAT has Packaging → Read access.
Your project .npmrc must scope the namespace with @strongtie:registry=… (and nothing more — public packages fall through to npm's default registry). Credentials live in ~/.npmrc. The full two-file setup is on Set up your .npmrc.
A bare registry=https://pkgs.dev.azure.com/… line (no @strongtie: prefix) causes auth errors for public packages — add the prefix.
Re-run authentication setup per the Azure Artifacts guide.
If you get authentication errors when installing public packages like tsdown, sonner, etc.:
In .npmrc, a registry=https://pkgs.dev.azure.com/… line without the @strongtie: prefix is the culprit.
Change it to @strongtie:registry=… so only the Simpson namespace routes through Azure Artifacts.
Run npm install again.
Remove build artifacts and reinstall: rm -rf node_modules package-lock.json && npm install.
Restart so it picks up the fresh dependency tree.
Ensure TypeScript 5.0 or newer is installed.
Set moduleResolution to "bundler" or "node16" in tsconfig.json.
In VS Code: Cmd/Ctrl + Shift + P → "TypeScript: Restart TS Server".