Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also orlearn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also.Learn more about diff comparisons here.
base repository:agilgur5/mst-persist
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base:v0.1.0
Choose a base ref
Loading
...
head repository:agilgur5/mst-persist
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare:v0.1.1
Choose a head ref
Loading
  • 15commits
  • 6files changed
  • 2contributors

Commits on Jul 18, 2019

  1. (docs): vertically condense badges by reducing spacing

    - felt like they took up too much space with the 4 sections now- had to change comment style to ensure the spacing works without  accidentally rendering the comments  - prev style required a new line to come immediately before
    @agilgur5
    agilgur5 committedJul 18, 2019
    Configuration menu
    Copy the full SHA
    81c5bb4View commit details
    Browse the repository at this point in the history

Commits on Jul 20, 2019

  1. (ci): add Travis CI support

    - don't have tests yet, so for now just test compile/build and pack  - modify the test script command to do so for now    - `npm test` is also the default script in Travis
    @agilgur5
    agilgur5 committedJul 20, 2019
    Configuration menu
    Copy the full SHA
    f254aafView commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    25b4cd2View commit details
    Browse the repository at this point in the history
  3. (pkg): add a Changelog that points to the GH Releases page

    - Some might not be aware that that's where it's hosted, so be explicit- Also be explicit that we use SemVer- in the future things might change and Changelog might be hosted here  so that it's independent from GitHub- and Changelog style might change to point out PRs, issues, etc,  instead of being mostly a list  - GH Release descriptions are unversioned, so style changes are    currently fluid as a result
    @agilgur5
    agilgur5 committedJul 20, 2019
    Configuration menu
    Copy the full SHA
    183dd90View commit details
    Browse the repository at this point in the history

Commits on Jul 27, 2019

  1. (pkg): add script to generate changelog for each release

    - makes my job easier and makes it possible for others to replicate  the same style changelog easily(deps): add @agilgur5/changelog-maker to devDeps- use my new fork of changelog-maker to make it a one-liner :)- alter repository.url so changelog-maker can read it properly
    @agilgur5
    agilgur5 committedJul 27, 2019
    Configuration menu
    Copy the full SHA
    9e01cefView commit details
    Browse the repository at this point in the history
  2. (pkg): reorder package.json fields

    - deps at the bottom always with scripts just above  - peerDeps, then deps, then devDeps    - add empty deps field for now as well- usage at the top and other info below  - homepage above repository and bugs  - author and license above homepage- basically just categorized this way for now
    @agilgur5
    agilgur5 committedJul 27, 2019
    Configuration menu
    Copy the full SHA
    4706dadView commit details
    Browse the repository at this point in the history
  3. (security): run npm audit fix on devDeps

    - updated lodash to fix advisories
    @agilgur5
    agilgur5 committedJul 27, 2019
    Configuration menu
    Copy the full SHA
    bd37065View commit details
    Browse the repository at this point in the history
  4. (fix): do not error if 'window' is undefined

    - in certain environments like Node, 'window' will not be defined and  so will cause mst-persist to error out on its check for localStorge,  even if a different storage engine were configured- this fix enables usage in Node environments, supporting usage like  hydrating server-side
    @barbalex@agilgur5
    barbalex authored andagilgur5 committedJul 27, 2019
    Configuration menu
    Copy the full SHA
    63053b9View commit details
    Browse the repository at this point in the history
  5. (fix): throw an error if no storage is configured

    - if the localStorage default is unsupported in the current  environment (e.g. Node), then it should throw with a specific  error instead of continuing and unexpectedly throwing on getItem  - will still error out, so not a "fix" in that sense, but it now will    throw a better, more understandable error
    @agilgur5
    agilgur5 committedJul 27, 2019
    Configuration menu
    Copy the full SHA
    a2f22a6View commit details
    Browse the repository at this point in the history
  6. Configuration menu
    Copy the full SHA
    6da8094View commit details
    Browse the repository at this point in the history
  7. (docs): note redux-persist's Storage Engines compatibility

    - redux-persist's Storage Engines all follow the same localForage-style  async Promise API, so they should all be compatible with mst-persist  as well  - docs should mention this as the interoperability adds many more    usage options for developers    - e.g. using node-storage or cookie-storage for Node or universal      apps, which should now work without bugs
    @agilgur5
    agilgur5 committedJul 27, 2019
    Configuration menu
    Copy the full SHA
    a36a41bView commit details
    Browse the repository at this point in the history
  8. (docs): add section on Node and SSR Usage

    - note that one can hydrate server-side with Node and give some example  storage engines one may use for that purpose- note that server-side hydartion can be skipped for certain use cases  like SSR and give example for how to do so
    @agilgur5
    agilgur5 committedJul 27, 2019
    Configuration menu
    Copy the full SHA
    2403d6eView commit details
    Browse the repository at this point in the history
  9. (docs/fix): track latest release by SemVer

    - in case a backport release is added, such as a backport of the  upcoming v0.1.1- "latest" in GitHub releases means latest by date, which means  backports are considered latest by definition  - using SemVer with the "tag" badge (not release anymore :/)    more or less resolves this for the README, but GH releases page    will always show by date :/- "commits since" is also currently tracking "latest" release by date  - no fix to this yet, c.f.badges/shields#1955 (comment)    - manually putting the latest SemVer tag for now :/ :/ :/ :/
    @agilgur5
    agilgur5 committedJul 27, 2019
    Configuration menu
    Copy the full SHA
    12ff92eView commit details
    Browse the repository at this point in the history
  10. (pkg): add a 'pub' script shortcut for build and publish

    - and gets rid of confusion for future me or future contributors  what the proper process for publishing is
    @agilgur5
    agilgur5 committedJul 27, 2019
    Configuration menu
    Copy the full SHA
    a7bb1fcView commit details
    Browse the repository at this point in the history
  11. (pub): publish v0.1.1

    - fixes/enables support for Node usage- adds docs for Node and SSR usage- adds docs note about compatibility w/ redux-persist Storage Engines- adds CHANGELOG.md that links to GH Releases page- various internal improvements  - adds Travis CI support  - adds changelog and pub scripts  - reorders package.json fields  - audit fixes devDeps  - makes docs track latest release by SemVer
    @agilgur5
    agilgur5 committedJul 27, 2019
    Configuration menu
    Copy the full SHA
    42357c0View commit details
    Browse the repository at this point in the history
Loading

[8]ページ先頭

©2009-2025 Movatter.jp