Releases: Esri/esri-loader
Make it easier to override lazy loaded ArcGIS styles
See https://github.com/Esri/esri-loader#overriding-arcgis-styles
Added
insertCssBeforeoption to insert CSS link before an existing element
Default to ArcGIS API 4.10
Thanks @jgravois!
Default to ArcGIS API 4.9
Changed
- default to JSAPI 4.9; update docs w/ latest version numbers - thanks @ziveo!
Default to ArcGIS API 4.8
Default to ArcGIS API 4.7
Added
- default to JSAPI 4.7; update docs w/ latest version numbers
Changed
- added Hyperapp example link to README
- move CSS functions into own module
- no longer publishing src folder b/c it is not needed
loadScript()/loadModules() take a `css` option to load a stylesheet
Added
loadScript()takes acssoption to load stylesheet by URL
Changed
- added Choo and Riot example links to README - thanks @jwasilgeo!
A little more style
Added
- added
loadCss(url)to inject a stylesheet link (thanks @SimplyAutomationized)
Changed
- added GitHub issue and pull request templates
- added badges to README
- added section on updating from previous versions to README
- added reusable library sections for Angular and React
- added links to ember-esri-loader examples and CanJS
- changed npm scripts to rely on rimraf and mkdirp for Windows support
- check in yarn.lockfile and use yarn
v2.0.0 - a slimmer new esri-loader for the new year!
Changed
- misc README updates
Breaking
- remove deprecated bootstrap() and dojoRequire() functions #59
- isLoaded() no longer checks if the script exists #59
- no longer distribute builds at dist root #59
In the spirit of Ember's principle of "stability without stagnation", this major release doesn't add any new functionality. It primarily removes the callback-based APIs (bootstrap() and dojoRequire()) that were deprecated at v1.5.0 in favor of the new promise-based APIs (loadScript() and loadModules()) introduced in that release.
There are a couple of additional breaking changes introduced in this release that there were no deprecation warnings for.
First, isLoaded() no longer checks for the existence of a script tag w/ the data-esri-loader attribute. Instead it checks for a global require() function that looks like Dojo's require(). This is the behavior that the new promise-based APIs have been using.
Second, the UMD build is no longer distributed at the root of the /dist folder - which could break build tooling that uses hard coded paths to that location (rather than relying on package.main).
All in all, most users that have been using only the new promise-based APIs introduced in v1.5.0 should be able to upgrade to 2.0 without any changes to their code and see a benefit in reduced file size.
See the CHANGELOG for history of changes from 1.5.0 to 2.0.0.
Special thanks to all the community members that have helped make v2.0 a reality, especially @nicksenger, @remotesc2, @tgeorges, @veonline, and @ziveo!
Please keep your suggestions and PRs coming!