- Fix: Update and pin
semver-regex
(will need to manually update) with suitable internal use; narrow ranges of other updated deps.; fixes #2 - Docs: Update CLI
- Docs: Update license badges
- npm: Update deps.
- Linting: As per latest ash-nazg
- Testing: Avoid new npm updating Yarn lock
- npm: Update package-lock to 2.0
- npm: Narrow devDep. ranges so shouldn't be updated anymore
- npm: Update devDeps.
- Fix: Missing space in CLI docs (LGTM-identified)
- Linting: Escape regexes for dots in URLs; avoid polynomial regex
- Fix: Do not allow downstream to use updated cheerio
- npm: Remove redundant Yarn override in CDN updating script
- Breaking change: Default of bootstrap now set to jsdelivr (boostrap CDN on
stackpath no longer being maintained);
packagesToCdns
still supports mapping tobootstrap
for the old CDN, though that may be removed in the future
- Update: Per new semver regex
- Linting: As per latest ash-nazg
- Docs: Example projects
- Docs: Update badges
- npm: Switch
prepare
toprepublishOnly
- npm: Use stable
mocha-multi-reporters
- npm: Update array.prototype.flat, domhandler, globby, htmlparser2, node-fetch, prompts, semver, semver-regex; devDeps
- Fix: Avoid overwriting
local
for JSON (server may need more precise path for its own purposes)
- Fix: semver check to support prerelease formats
- Enhancement: Add
dropBase
option for dropping<base href>
in dev. file - Docs: Update docs on
cdnName
from CLI
- Breaking change: Require slim and min to paths (allowing dropping of min)
- Fix: For
fortawesome/fontawesome-free
CDN, ensure droppingmin
- Breaking change: Let JSON format accept an array of links and scripts
- Testing: Add case where name is repeated (multiple fontawesome links under attribute-control test)
- Enhancement: Support
@fortawesome/fontawesome-free
CDN
- Docs: Update CLI docs to document
ext
- Fix: Proper jquery CDN mapping
- Testing: Check default bootstrap and jquery for convertability from
node_modules
- Testing: Avoid hard-coding bootstrap version in test file; adjust fixtures
- npm: Add script for reapplying yarn changes
- npm: Update devDeps
- Fix: Force
integrity
to be added whendata-im-algorithms
present even when nointegrity
in source.
- Enhancement (HTML and JSON): Use
data-im-*
attributes / JSON property for in-data config (algorithms
)
- Enhancement (HTML): Use
data-im-*
attributes in HTML for in-data config (cdn
,global
, and auto-setfallback
ifglobal
present) - Enhancement (JSON): Support
cdn
inline override
- Breaking change: Expect
dist
normally in replacement paths (unless omitted from result) - Enhancement:
cdnName
andpackagesToCdns
options - Enhancement:
DomHandler
orhtmlparser2
options - Enhancement:
jsonSpace
option - Enhancement: Add
dropModules
option - Enhancement: Add
disclaimer
option - Refactoring: Have Strategy's
save
accept an object
- Fix: Ensure
rel="stylesheet"
added to fallback links
- Fix: Preserve relative path characters at beginning of
node_modules
paths (for output)
- Fix: Have regexes handle scoped packages
- Change (JSON): Add newline to JSON
- Change: Drop dep. vs. devDep. checking (not a critical issue for our scope of concern)
- Fix: Throw if
package.json
cannot be reached - Fix: Properly handle missing
integrity
- Fix: Avoid stray apostrophe in log/error
- Fix (JSON): Handle JSON missing
script
orlink
- Fix (JSON): Avoid setting crossorigin to
false
- Fix (JSON): Reorder to set
crossorigin
with its integrity check before changing integrity - Enhancement: Add
urlIntegrityCheck
- Testing: Improve coverage
- Testing: Ensure deleting output path before each run
- Fix:
node_modules
-> CDN paths - Fix: Check yarn lock dependency info properly
- Fix: Give warning if
yarn.lock
andpackage-lock.json
both installed; don't give extra info on yarn if package-lock found and noyarn.lock
found (as is expected) - Fix: Avoid removing
integrity
beforeelem.is([integrity])
check (may need to altercrossorigin
) - Refactoring: Add period in error message for consistency
- Testing: Fix expected (ternary precedence issue)
- Testing: Improve coverage
- Fix: Avoid bad replacement if
forceIntegrityChecks
forces integrity change with no version change found - Fix: Properly handle case where targeted package missing in
package.json
dependencies - Fix: Throw instead of warning when package not present in
node_modules
(withpackage.json
) - Testing: Improve coverage
- Fix: Ensure
false
crossorigin
removes the attribute - Testing: Improve coverage
- Fix: Add
flat
polyfill - Fix: Throw if local
node_modules
path not found for matching CDN - Fix: Throw for bad CDN status code
- Fix: Do proper filtering of hashes when any are removed
- Enhancement: Have
cdnBasePathReplacements
andnodeModulesReplacements
default to first item in array if not present - Enhancement: Throw instead of silently ignoring some bad integrity matches
- Testing: Improve coverage
- Testing: Delete outputPath before and after tests
- CI: Ensure folder exists
- Fix: Add
flat
polyfill - CI: Ensure folder exists
- Fix: Avoid using globs when
outputPath
is set and need fornoGlobs
when usingoutputPath
; print proper path - Enhancement: Log file path when finished writing file
- Enhancement: Deterministic logging order
- Initial version