-
-
Notifications
You must be signed in to change notification settings - Fork 879
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prepare for canary release #352
Merged
Merged
Commits on Jan 16, 2020
-
Configuration menu - View commit details
-
Copy full SHA for c37a518 - Browse repository at this point
Copy the full SHA c37a518View commit details -
Configuration menu - View commit details
-
Copy full SHA for fb47a9d - Browse repository at this point
Copy the full SHA fb47a9dView commit details
Commits on Jan 20, 2020
-
Apparently the changelog for v3.3.3 was edited manually and had a bad heading level
Configuration menu - View commit details
-
Copy full SHA for 26987bc - Browse repository at this point
Copy the full SHA 26987bcView commit details -
chore: rename package script to build
"build" seems to be the more appropriate term for what we're doing here. Part of #343.
Configuration menu - View commit details
-
Copy full SHA for 4244b9e - Browse repository at this point
Copy the full SHA 4244b9eView commit details
Commits on Jan 21, 2020
-
chore: transition dev dependencies to exact versions
Since the devDependencies are pinned in the package-lock.json anyways there's no real use in leaving a version range open for the devDependencies in package.json. Instead, we simply keep our toolchain up-to-date with tools like ncu. With this commit I also re-generate package-lock.json from scratch.
Configuration menu - View commit details
-
Copy full SHA for 4bd4fd7 - Browse repository at this point
Copy the full SHA 4bd4fd7View commit details -
Configuration menu - View commit details
-
Copy full SHA for f2c361d - Browse repository at this point
Copy the full SHA f2c361dView commit details -
Configuration menu - View commit details
-
Copy full SHA for 06436a7 - Browse repository at this point
Copy the full SHA 06436a7View commit details -
build: set up and document build and release scripts
Since we have a build step now we must point the package.json file reference to the dist folder and must explicitly list all files that we want to be included in the npm tarball. The initial idea was to prepare the contents of the final npm tarball all in the dist directory (including a copy of the package.json) but that turns out not to work particularly well with standard-version which is used to manage the version numbers and changelog. Unfortunately this change also required a small workaround to allow local installation of the uuid module in the examples (see .local/). Also instructions for relasing a new version have not yet been documented which is finally done here. Since we now explicitly list all files to be included in the tarball through the files property of package.json we no longer need the .npmignore file.
Configuration menu - View commit details
-
Copy full SHA for 53ca9d4 - Browse repository at this point
Copy the full SHA 53ca9d4View commit details
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.