Is it just me or does

gulp theme:deploy --source sass

do nothing? It goes through the whole process, but doesn’t seem to actually change any sass files, even after reactivation of the theme… Also, for any NetSuite folks that might be lurking (@Steve Goldberg maybe), the documentation for gulp lists

gulp extension:deploy --source <multiple>

under the theme section. (Not that this command seems to do anything anyway…)

@Jacob D are you performing a cache invalidation after you perform the deploy? I always perform a cache invalidation after deploying anything. I also work with a private/incognito browser and perform a hard refresh/clear cache data after a deploy.

@Keith Fetterman I’m working in sandbox where the CDN is turned off, so cache invalidation isn’t really an issue

Even though the CDN is turned off NetSuite’s servers also perform caching. The cache invalidation also clears the NetSuite cache. I have had to use it when deploying ssp libraries.

@Keith Fetterman So I would perform the cache invalidation after activation, I assume?

Hi @Jacob D, correct. when the activation is completed, perform the cache invalidation for all paths of the domain you are working with. Let me know if it worked. I have not used “--source” with gulp theme:deploy or gulp extension:deploy. I have used “--source” when using gulp to deploy SCA. When I used “--source” with gulp to deploy ssp-libraries, my updated ssp-libraries didn’t work until after I performed the cache invalidation. I discovered a long time ago that NetSuite’s servers were also caching data even when CDN was turned off. I hope this works for you. Good luck.

@Keith Fetterman Tried the cache invalidation after theme activation. Still nothing. Oh well, looks like I’m stuck doing a full

gulp theme:deploy

every time. There was a time when I was actually excited about the prospect of the extensibility layer…

If you think it is malfunctioning, please raise a support case.

That’s a bummer. It takes a long time to deploy a theme. Thanks for letting me know.