![]() ![]() The different CDNs may have a different syntax for controlling the version numbers. This puts me in control of the testing and I'm more confident that any bugs in the application will be a result of my coding, rather than an update to a library used in the project. I import the three libraries I use at specific versions: when using multiple versions of libraries, future versions may conflict with each other, again causing your application to fail in production and possibly without you noticing.If you deploy to production and allow the version to change with every new release, then your application may gradually exhibit bugs or incompatibilities over time because you haven't tested your application against the new version of the library. you will have tested your application on a specific version.There are number of advantages to controlling the version: As you can see from the src URL below I included version 5.5.3: So if my code had been defaulting to the latest version then my application would have failed.įortunately I had imported a specific version of faker from unpkg. In my open source table editing tool I use three libraries: AG Grid, PapaParse, and Faker.įaker recently had an issue where a recent version deployed to npm had issues. How (and Why) to Control the Version of the Library īoth of these CSS files are also deployed to and can be included into our project from a CDN. ![]() The Theme Style sheet provides the visual aesthetics for the Grid. The Structural Style sheet provides the CSS that will layout the data as a Grid. ![]() These would be referenced from the CDN as normal using link elements.įor example, AG Grid uses two style sheets. For example, AG Grid deploys CSS files as well as JavaScript.
0 Comments
Leave a Reply. |