But what strategies can you follow to mitigate those risks when building your websites? The best strategy of course for mitigating risks, is to eliminate the risk factor entirely. In practice, this means that you need to question yourself whether you actually need the external library or if you could leverage web standards functionality. The second strategy is to contain the risk by making sure you follow up on updates, making sure you always upgrade to the latest stable version of each library.
This blogpost is the second in a series about Modern Web development. We’ll be covering the following topics:
- CSS prefixes
- Browser and feature detection
- Rendering modes
Replacing jQuery functionality
In the following example, we’ll demonstrate how to replace DOM manipulations with web standards functionality. In the code sample below you can see some examples of doing this using jQuery.
As mentioned, sometimes you need to use an external library because it provides functionality that is not provided through web standards.
Web standards have evolved over time and some functionality previously provided through external libraries are now available in the web standard and are available cross-browser and cross-platform.
- Check out the Microsoft Edge Developer Center for valuable resources and tools when working with the Microsoft Edge browser.
- An in-depth overview on how to scan your site using the site scanner.
- View our complete video on Channel 9: Riding the Modern Web: Five things to consider as a web developer
- Download Visual Studio Code for free for a great cross-platform coding experience for web developers. Also check out our webinar on how to get started with Visual Studio Code.
For an overview of the 5 things to consider when developing for the modern web, check out our 17-minute video.