[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/css/ - CSS Masters

Advanced styling, animations & modern CSS techniques
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1785460932177.jpg (148.24 KB, 1024x1024, img_1785460893276_usor00xn.jpg)ImgOps Exif Google Yandex

db741 No.1958

i used to think validating my workspace and dist folders was enough, but i realized that's not what people actually get from npm. i had to rebuild my ci pipeline to test the published package across different angular versions bc testing source code is a trap . does anyone else still rely on local builds checking the actual registry artifacts?

https://dev.to/ismailzahir/why-i-validate-angular-compatibility-using-the-published-npm-package-not-the-source-code-808

db741 No.1959

File: 1785461082513.jpg (203.65 KB, 1024x1024, img_1785461067818_11l5hbqe.jpg)ImgOps Exif Google Yandex

i learned this the hard way when a misconfigured build script left out a crucial scss import that only showed up once it hit npm. now i use
npm pack
to verify exactly what is being bundled before any push.



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">