Merge pull request #517 from xmtp/main

`main` => `beta`

.eslintignore

@@ -1,5 +1,3 @@
-*.config.js
-*.config.ts
 *.test.js
 *.test.ts
 dist

.gitignore

@@ -125,3 +125,6 @@ tmp/
 
 # Benchmark results
 bench/results
+
+# rollup build plugin output
+build/rollup-plugin-resolve-extensions/index.js

.node-version

@@ -0,0 +1 @@
+18.14.0

.prettierignore

@@ -2,3 +2,4 @@ dist
 coverage
 docs
 tmp
+build/rollup-plugin-resolve-extensions/index.js

CODE_OF_CONDUCT.md

@@ -0,0 +1,43 @@
+# XMTP code of conduct
+
+This code of conduct applies within all XMTP community spaces, virtual and physical, and also applies when an individual is officially representing the XMTP community in public spaces. Examples of representing our community include using an official email address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Our pledge
+
+We as members pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our conduct
+
+Examples of behaviors that contribute to a positive environment for our community include:
+
+- Demonstrating empathy and kindness toward other people
+- Being collaborative and respectful of differing opinions, viewpoints, and experiences. A great protocol is built by many contributors learning and working together.
+- Being bold yet intentional when presenting ideas. We are here to help ensure the world has access to secure and private communication, while also acknowledging that building successful protocols and ecosystems requires the application of logic and evidence.
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+- Focusing on what is best not just for us as individuals but for the overall community, and the people depending on XMTP for communication.
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery, and sexual attention or advances of any kind
+- Hate speech, trolling, shitposting, flaming, spamming, unsolicited advertising, baiting, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others’ private information, such as a physical or email address, without their explicit permission
+
+## Moderation
+
+Community moderators are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community moderators have the right and responsibility to remove, edit, or reject comments, commits, code, issues, and other contributions that are not aligned to this code of conduct and will communicate reasons for moderation decisions when appropriate.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior can be reported to the community moderators responsible for enforcement at [[email protected]](mailto:[email protected]). All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. All community moderators are obligated to respect the privacy and security of the reporter of any incident.
+
+Community moderators who do not follow or enforce the code of conduct in good faith may face temporary or permanent repercussions as determined by other community moderators.
+
+## Attribution
+
+The XMTP code of conduct is adapted from the Contributor Covenant, [version 2.1](https://www.contributor-covenant.org/version/2/1/code_of_conduct.html) and [version 1.4](https://www.contributor-covenant.org/version/1/4/code-of-conduct.html).

CONTRIBUTING.md

@@ -1,32 +1,48 @@
 # Contributing
 
-If you're seeing this document, you are an early contributor to the development and success of XMTP. We welcome your questions, feedback, suggestions, and code contributions.
+Thank you for considering contributing to this repo! Community contributions like yours are key to the development and adoption of XMTP. Your questions, feedback, suggestions, and code contributions are welcome!
 
 ## ❔ Questions
 
-Have a question? We welcome you to ask it in [Q&A discussions](https://github.com/orgs/xmtp/discussions/categories/q-a).
+Have a question about how to build with XMTP? Ask your question and learn with the community in the [XMTP Community Forums](https://community.xmtp.org/).
 
 ## 🐞 Bugs
 
-Bugs should be reported as GitHub Issues. Please confirm there isn't already an open issue and include detailed steps to reproduce.
+Report a bug using [GitHub Issues](https://github.com/xmtp/xmtp-js/issues).
 
 ## ✨ Feature Requests
 
-These should also be submitted as GitHub Issues. Again, please confirm there isn't already an open issue. Let us know what use cases this feature would unlock so that we can investigate and prioritize.
+Request a feature using [GitHub Issues](https://github.com/xmtp/xmtp-js/issues).
 
 ## 🔀 Pull Requests
 
-PRs are encouraged, but we suggest starting with a Feature Request to temperature-check first. If the PR would involve a major change to the protocol, it should be fleshed out as an [XMTP Improvement Proposal](https://github.com/xmtp/XIPs/blob/main/XIPs/xip-0-purpose-process.md) before work begins.
+PRs are encouraged, but consider starting with a feature request to temperature-check first. If the PR involves a major change to the protocol, the work should be fleshed out as an [XMTP Improvement Proposal](https://community.xmtp.org/t/xip-0-xip-purpose-process-guidelines/475) before work begins.
+
+After a pull request is submitted, a single approval is required to merge it.
 
 ## 🔧 Developing
 
-### Testing and validation
+### Prerequisites
+
+#### Node
 
-Please add unit tests for your feature, and ensure that all unit tests are passing before submitting a pull request. All test commands are described in `package.json` and executed via `npm run <command>`. Note that the unit tests require a backend node to be running locally - the `test:setup` step can be run a single time to start the node in the background, and `test` can be run as many times as desired afterwards.
+Please make sure you have a compatible version as specified in `package.json`. We recommend using a Node version manager such as [nvm](https://github.com/nvm-sh/nvm) or [nodenv](https://github.com/nodenv/nodenv).
 
-Manual validation requires setting up a client app such as the [example app](https://github.com/xmtp/example-chat-react). Once you have cloned and run the example app, it will use a published npm version of `xmtp-js` by default. You can point it to your local `xmtp-js` repository by running `npm i file:~/path/to/xmtp-js` from the `example-chat-react` directory, which will update its `package.json`. Once the example app is running, any further changes you make to `xmtp-js` will be reflected in the app after you run `npm build` in the `xmtp-js` directory and then reload the app.
+### Useful commands
 
-After a pull request is submitted, a single approval is required to merge it.
+- `npm install`: Installs all dependencies
+- `npm run bench`: Run the benchmarking suite
+- `npm run build`: Builds all SDK packages
+- `npm test`: Run the unit test suite
+- `npm run test:setup`: Start a local development node using Docker (only needs to be run once)
+- `npm run lint`: Lint with ESLint
+- `npm run typecheck`: Typecheck with `tsc`
+
+### Testing and validation
+
+Please add unit tests when appropriate and ensure that all unit tests are passing before submitting a pull request. Note that some unit tests require a backend node to be running locally. The `test:setup` command can be run a single time to start the node in the background using Docker.
+
+Manual validation requires setting up a client app such as the [example app](https://github.com/xmtp/example-chat-react). Once you have cloned and run the example app, it will use a published npm version of `xmtp-js` by default. You can point it to your local `xmtp-js` repository by running `npm i file:~/path/to/xmtp-js` from the `example-chat-react` directory, which will update its `package.json`. Once the example app is running, any further changes you make to `xmtp-js` will be reflected in the app after you run `npm run build` in the `xmtp-js` directory and then reload the app.
 
 ### Auto-releasing and commit conventions
 
@@ -54,17 +70,3 @@ If your commit messages are not to your liking, it is permitted to rewrite the h
 [push]
 	default = simple
 ```
-
-### Prerequisites
-
-#### Node
-
-Please make sure you have a Node version compatible with that specified in the root `.nvmrc` file. We recommend using `nvm` to manage local node versions - find install instructions appropriate for your system [here](https://github.com/nvm-sh/nvm#installing-and-updating).
-
-#### Buf
-
-You will need to install [Buf](https://buf.build/) in your environment in order to `npm build` this package from source.
-
-```bash
-brew install bufbuild/buf/buf
-```

build/rollup-plugin-resolve-extensions/index.ts

@@ -0,0 +1,43 @@
+import { basename, dirname, extname, format } from 'node:path'
+import { existsSync } from 'node:fs'
+import { Plugin } from 'rollup'
+import { getResolvedPath, loadCompilerOptions } from '../utils'
+
+export const resolveExtensions = (
+  extensions: string[] = [],
+  tsconfigPath?: string
+): Plugin => {
+  const compilerOptions = loadCompilerOptions(tsconfigPath)
+  return {
+    name: 'resolve-extensions',
+    async resolveId(source, importer, options) {
+      if (extensions.length && !options.isEntry && importer) {
+        const resolvedPath = getResolvedPath(source, importer, compilerOptions)
+        let updatedSource = ''
+
+        if (resolvedPath) {
+          const ext = extname(resolvedPath)
+          const base = basename(resolvedPath, ext)
+          const dir = dirname(resolvedPath)
+          // check for extensions
+          extensions.some((extension) => {
+            const newPath = format({
+              dir,
+              name: base,
+              ext: `${extension}${ext}`,
+            })
+            const exists = existsSync(newPath)
+            if (exists) {
+              updatedSource = newPath
+              return true
+            }
+            return false
+          })
+
+          return updatedSource || null
+        }
+      }
+      return null
+    },
+  }
+}