Troubleshooting Installation

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.

Styles not loading

Ensure @strongtie/design-system/styles is imported in your entry file
Check import order - styles should come before component usage
Clear build cache and restart dev server

Authentication errors

Verify your Azure DevOps PAT has Packaging > Read permissions

Check .npmrc configuration should have scoped registry:

cat .npmrc
# Should show:
# @strongtie:registry=https://pkgs.dev.azure.com/StrongTie/_packaging/Simpson/npm/registry/
# @strongtie:always-auth=true
# registry=https://registry.npmjs.org/

If you see registry= without @strongtie: prefix, you have the wrong config (this will cause auth errors for public packages)
Re-run authentication setup following the Azure Artifacts guide

E401 Authentication errors for public packages

If you get authentication errors when installing public packages like tsdown, sonner, etc.:

Check your .npmrc - if it has registry=https://pkgs.dev.azure.com/... (without @strongtie: prefix), this is the problem
Update to use scoped registry as shown in Step 1 above
Run npm install again

Module not found

Clear node_modules and reinstall:

rm -rf node_modules package-lock.json
npm install

Restart your dev server

TypeScript errors

Ensure TypeScript 5.0+ is installed
Set moduleResolution to "bundler" or "node16" in tsconfig.json
Restart TypeScript server: Cmd/Ctrl + Shift + P > "TypeScript: Restart TS Server"

@strongtie/styles Design Systems at Simpson Strong-Tie

On This Page

Styles not loading Authentication errors E401 Authentication errors for public packages Module not found TypeScript errors

Contribute