Over the last couple weeks, I’ve been to working on two things:
Refreshing of my Mastering the SharePoint Framework course… I’ve completely re-recorded the Starter bundle. I’m working on the lessons now & looking forward to updating what’s currently there. More on that later…
In this post, I want to tell you about some of this modernization work I’ve been doing and how you can apply it to your SPFx projects!
Microsoft has been slow to keep SPFx current with modern development. Part of the reason is due to the fact they have to worry about enterprises with corporate standards, but a good bit is just their lack of “keeping up.”
Let me share a few things with you that you can apply to your SPFx projects TODAY & not wait on Microsoft to get with the times.
SPFx projects today, even the SPFx v1.13 betas, still use TSLint as their code linter.
So why is SPFx still using TSLint in its default project scaffolding? We’ve had seven SPFx releases since those announcements… so… what’s the hold up?
You know what, it doesn’t matter… you can address it in your projects today without waiting.
In my post 👉 Get with the times & ditch TSLint in favor of ESLint in SharePoint Framework projects, I explain what’s involved and how to make a few changes to adopt ESLint and ditch TSLint.
@andrewconnell created presets for #SharePoint Framework projects to use #ESLint & ditch the long-deprecated #TSLint tool that Microsoft includes in #SPFx projects. All you have to do is install a single NPM package and you're automatically using ESLint! https://t.co/3plfSob4bN pic.twitter.com/SCOCMsGUdw— Voitanos (@voitanos) August 4, 2021
After I wrote blog post, I thought to myself “I wonder if there’s an easier option for developers to make this change?” Sure enough there is!
Following a similar pattern with my Jest presets for SPFx projects, I created a preset for swapping out TSLint in favor of ESLint. All you have to do is install a single NPM package after creating your project. You can learn more about this in my post 👉 Ditch TSLint for ESLint in SPFx projects in one simple step.
But that’s not all…
Did you know that earlier this month, Microsoft finally pulled the plug on IE11 support for all Microsoft 365 apps? That means if you’re building SPFx projects for use in SPO, there’s absolutely ZERO reason to support IE11… because your hosting environment doesn’t support IE11.
Interested in learning more about this as well as how to make this change? Check out my post 👉 Optimize bundles by disabling IE11 support in SPFx projects.
Continuing with @andrewconnell's theme of recent posts, learn how to optimize #SharePoint Framework bundles by ditching support for #IE11. You can do this thanks to Microsoft ditching IE11 from the supported browsers for all apps in #Microsoft365! #SPFx https://t.co/SUV1yOz7j5 pic.twitter.com/IK8CwuCgPj— Voitanos (@voitanos) August 24, 2021
And if you’re wondering if this is a good idea, rest assured… even Microsoft supports it:
comments powered by Disqus
Create guidance on reducing the bundle sizes for #SPFx solutions for #MicrosoftViva, #MicrosoftTeams and #SharePoint.— Vesa Juvonen (@vesajuvonen) August 24, 2021
Simple way to optimize the solution structure. We'll look into doing this also natively in the default projects now that IE11 support is gone.#Microsoft365dev https://t.co/kXRkcQMlSY