Repository navigation
Conversation
- Maintenance: Add `.editorconfig` - Linting: Prefer const, no-var, fix indent, comment-out unused - npm: Add eslint devDep. and script - npm: Set engines to 10.11.0+ - npm: Add lock file
… non-null serverInfo
Prevents uncaught exception: TypeError [ERR_INVALID_ARG_VALUE]: The argument 'path' must be a string or Uint8Array without null bytes.
- npm: Change to 0.1.0 version
- ncu: Add `.ncurc.js` to prevent `mime` being reported for updates (2.0 seems may be buggy and would need to investigate)
Switched to a different option parser to keep things simple
…le access vulnerability - https://www.npmjs.com/advisories/1206
* Keep backwards compatibility with previous cache options * Add tests to ensure glob matching with defined cache values * Updated README with instructions for new cache feature
…semantically marked-up headings and add CLI options; closes cloudhead#177
Also: - Docs: Update CHANGES
BREAKING CHANGE: Requires Node 12
…ath (such as a hash); fixes cloudhead#170
…, avoiding vulnerability
- **Breaking change**: Add type: 'module' and exports to `package.json`;
change internal CJS path
- Refactoring: Switch to ESM
- Update: Switch from deprecated `request` to `node-fetch`
- Testing: Switch to `mocha`/`chai`/`c8`
- Testing: Begin binary file coverage
- Docs: Add ESM file-server example
|
Because I had not been feeling well at the time you made these updates, I had forgotten about your work on this, so continued forward with some rebases upon resuming work on the project. However, in looking at your work, I was unclear about your information on My own approach to avoid the conflicts was to graft in new commits with the same contents in place of the merge commits (though referencing the original merge info in the commit messages). This did cause loss of commit author information within a handful of commits, but credits are listed in the changes file, and again, the commits do reference the merge info. For some reason I am unable to load your repo. If it's ok, @cloudhead , I can force |
|
That's fine by me! The only thing I'd like fixed as well is the formatting of the commit messages: some commits eg. |
|
@cloudhead Cool. I've applied to There are only a few |
|
@cloudhead : Any chance we can get a release now? Thanks! |
@cloudhead mentioned in #224 that he had trouble cleaning the Git history because of all the merges. This tree converts all merges since brettz9 took over into squashes and rebases, for a linear commit history for all commits since 83aac2e.
The way I did this was by repeatedly running
git rebase -i --rebase-merges 83aac2e. Trying to convert merges into squashes/rebases from earliest to latest led to merge conflicts, but converting them from latest to earliest was possible with no conflicts.You should be able to use my rebases: