Merge upstream master branch into Soroban.
#636
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# Building Webpack 5 support is here! - the node package is built using Babel via `yarn build:node` - the browser bundle is built using Webpack via `yarn build:browser` * this is configured in `cfg/webpack.config.browser.js` * its accessible after including the script via the `StellarBase` variable * it adds a handful of important polyfills * it does linting via ESLint # Linting ESLint, Prettier, and DTSLint are all updated: - ESLint works with Babel via the `@babel/eslint-parser` in each `.eslintrc.js` file and is implicitly part of building via Webpack (see above) - DTSLint is part of the `@definitelytyped` project and has additional configuration implicitly as part of the `types/.eslintrc.js` file which uses `@typescript-eslint/parser`, instead - Prettier is configured in `cfg/prettier.config.js` (and `cfg/.prettierignore`) and runs on all files now. It's also (still) a pre-commit hook. Just run `yarn pretty && yarn lint` to format your files and check that everything is up to par. # Testing **Istanbul**: Istanbul is [unmaintained](https://www.npmjs.com/package/istanbul) and superceded by the `nyc` package. - the `istanbul` plugin in `.babelrc` tells Babel about it - `cfg/.nycrc` extends a Babel-compatible configuration file ([docs](https://github.com/istanbuljs/nyc#babel-projects)) - the `nyc` key in `package.json` configures instrumentation behavior - the coverage is *actually* provided by `babel-plugin-istanbul` ([docs](https://github.com/istanbuljs/babel-plugin-istanbul)), which is why `"instrument": false` in the above **Node Testing**: Mocha (and its helper friends Sinon and Chai) has been updated. - the `mocha` key in `package.json` configures Mocha (replacing `mocha.opts`) - this does Babel transpiling and hooks in the helper script - code coverage is provided by `nyc` (see above) **Browser Testing**: Karma has been updated. - the SauceLabs Karma configuration has been removed entirely because it wasn't being used - Karma has been updated with a code coverage integration with `nyc` ([docs](https://github.com/istanbuljs/babel-plugin-istanbul#karma), see above) - It relies on the Webpack configuration but makes some minor changes Run `yarn test` to run both suites. # Scripts Development has a slightly different workflow now: - build+test locally with `yarn test:node` - this will only run node tests (which are faster/simpler) - you can `yarn build && yarn test:all` to get the both test suites (note that building first is *required*) - run `yarn preversion` when you want a thorough, clean test of the whole system in "production" mode
* Add the hacky namespace workarounds we use
* Drop overloaded Operation in next.d.ts
* Add fully-qualified type (Operation is wrong) * Add changelog & version bump
Bumps [yaml](https://github.com/eemeli/yaml) from 2.2.1 to 2.2.2. - [Release notes](https://github.com/eemeli/yaml/releases) - [Commits](eemeli/yaml@v2.2.1...v2.2.2) --- updated-dependencies: - dependency-name: yaml dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [engine.io](https://github.com/socketio/engine.io) from 6.4.1 to 6.4.2. - [Release notes](https://github.com/socketio/engine.io/releases) - [Changelog](https://github.com/socketio/engine.io/blob/main/CHANGELOG.md) - [Commits](socketio/engine.io@6.4.1...6.4.2) --- updated-dependencies: - dependency-name: engine.io dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…). (#592) * Upgrade js-xdr, dependency upgrade, GHA fixups: - `js-xdr` set to v2.0.0 - `yarn upgrade-interactive --latest` - `rm yarn.lock && yarn` - GHAs enhanced to work around `yarn` bugs? - CHANGELOG entry + version bump added
* Update asset sorting method to match other sdk's I update the asciicompare function to properly sort upper case letters before lower case regardless of their position of the alphabet. * Update asset.js each is a string not a number, but we need a number to properly compare the length so we set a variable called letter pos using parseInt(each) * npm run fmt * Use Buffer.compare * Review feedback --------- Co-authored-by: Silence <35656692+silence48@users.noreply.github.com>
Bumps [socket.io-parser](https://github.com/socketio/socket.io-parser) from 4.2.2 to 4.2.3. - [Release notes](https://github.com/socketio/socket.io-parser/releases) - [Changelog](https://github.com/socketio/socket.io-parser/blob/main/CHANGELOG.md) - [Commits](socketio/socket.io-parser@4.2.2...4.2.3) --- updated-dependencies: - dependency-name: socket.io-parser dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
tsachiherman
approved these changes
Jul 3, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The impact is minimal (dropping some deps, small bugfixes; see PR diff view), but keeping the branches in sync is generally a Good Idea:tm: