Mea culpa - always install gulp-cli globally, not gulp

This is a story about a mea culpa. That’s me saying “I got it wrong and I want to fix it”, and while I’m not speaking for Microsoft on my blog, I believe I’m also speaking for them as well. For the longest time, SharePoint Framework (SPFx) developers were told to install gulp globally when setting up their development environment. However, that’s been wrong all along. You should have been installing the gulp-cli package globally (as the docs show), not gulp globally. To better understand why, keep reading.

This is a story about a mea culpa. That’s me saying “I got it wrong and I want to fix it”, and while I’m not speaking for Microsoft on my blog, I believe I’m also speaking for them as well.

For the longest time, SharePoint Framework (SPFx) developers were told to install gulp globally when setting up their development environment. However, that’s been wrong all along. You should have been installing the gulp-cli package globally ( as the docs show ), not gulp globally.

To better understand why, keep reading.

This article first appeared on the Voitanos blog: Mea culpa - always install gulp-cli globally, not gulp

This is a story about a mea culpa. You should have been installing the gulp-cli package globally, not #gulp globally. To better understand why, keep reading. #meaculpa #nodejs #microsoft365dev #sharepointframework #spfx https://t.co/fGwb38Yief pic.twitter.com/PT8nbKVZHs
— Voitanos (@voitanos) February 1, 2022