init commit

.cargo/config.toml

@@ -0,0 +1,33 @@
+[env]
+CARGO_WORKSPACE_DIR = { value = "", relative = true }
+NRZ_PNPM_WORKSPACE_DIR = { value = "", relative = true }
+
+[build]
+rustflags = [
+  "--cfg",
+  "tokio_unstable",
+  "-Zshare-generics=y", # make the current crate share its generic instantiations
+  "-Zthreads=8", # parallel frontend https://blog.rust-lang.org/2023/11/09/parallel-rustc.html
+  "-Csymbol-mangling-version=v0",
+]
+rustdocflags = ["-Znormalize-docs"]
+
+[target.x86_64-pc-windows-msvc]
+linker = "rust-lld"
+
+[target.aarch64-pc-windows-msvc]
+linker = "rust-lld"
+
+[target.'cfg(target_os = "macos")']
+linker = "rust-lld"
+
+[target.'cfg(all(target_os = "linux", target_env = "gnu"))']
+rustflags = [
+  "--cfg",
+  "tokio_unstable",
+  "-Zshare-generics=y",
+  "-Zthreads=8",
+  "-Csymbol-mangling-version=v0",
+  "-Clink-arg=-fuse-ld=lld",
+]
+

.devcontainer/Dockerfile

@@ -0,0 +1,33 @@
+# See here for image contents: https://github.com/microsoft/vscode-dev-containers/tree/v0.233.0/containers/go/.devcontainer/base.Dockerfile
+
+# [Choice] Go version (use -bullseye variants on local arm64/Apple Silicon): 1, 1.16, 1.17, 1-bullseye, 1.16-bullseye, 1.17-bullseye, 1-buster, 1.16-buster, 1.17-buster
+ARG VARIANT="1.18-bullseye"
+FROM mcr.microsoft.com/vscode/devcontainers/go:0-${VARIANT}
+
+RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \
+  && apt-get -y install --no-install-recommends \
+  # Chromium for running Nrzpack benchmarks
+  chromium \
+  # Used for plotters graph visualizations in nrzpack benchmarks
+  libfontconfig1-dev
+
+# Add hyperfine, a useful benchmarking tool
+RUN dpkgArch="$(dpkg --print-architecture)"; \
+  wget "https://github.com/sharkdp/hyperfine/releases/download/v1.12.0/hyperfine_1.12.0_${dpkgArch}.deb" && dpkg -i "hyperfine_1.12.0_${dpkgArch}.deb"
+
+#
+# Everything below is run as the vscode user. If superuser permissions are necessary,
+# run it before this. Otherwise, prefer running as the vscode user.
+#
+USER vscode
+
+# [Choice] Node.js version: none, lts/*, 16, 14, 12, 10
+ARG NODE_VERSION="none"
+RUN if [ "${NODE_VERSION}" != "none" ]; then umask 0002 && sh -c ". /usr/local/share/nvm/nvm.sh && nvm install ${NODE_VERSION}" 2>&1; fi
+
+RUN sh -c ". /usr/local/share/nvm/nvm.sh && npm install -g vercel yarn yalc pnpm nodemon" 2>&1
+
+# The installer from https://rustup.rs/ homepage, with the following changes:
+#   * `-y` to accept without interactivity
+#   * `--default-toolchain none` to avoid installing stable rust. Our specific toolchain is installed post-create.
+RUN curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh -s -- -y --default-toolchain none

.devcontainer/devcontainer.json

@@ -0,0 +1,52 @@
+// For format details, see https://aka.ms/devcontainer.json. For config options, see the README at:
+// https://github.com/microsoft/vscode-dev-containers/tree/v0.233.0/containers/go
+{
+  "name": "nrz (go, node, rust)",
+  "build": {
+    "dockerfile": "Dockerfile",
+    "args": {
+      // Update the VARIANT arg to pick a version of Go: 1, 1.18, 1.17
+      // Append -bullseye or -buster to pin to an OS version.
+      // Use -bullseye variants on local arm64/Apple Silicon.
+      "VARIANT": "1.18-bullseye",
+      // Options
+      "NODE_VERSION": "lts/*"
+    }
+  },
+  "runArgs": [
+    "--cap-add=SYS_PTRACE",
+    "--security-opt",
+    "seccomp=unconfined"
+  ],
+  // Add the IDs of extensions you want installed when the container is created.
+  "extensions": [
+    "bradlc.vscode-tailwindcss",
+    "christian-kohler.npm-intellisense",
+    "dbaeumer.vscode-eslint",
+    "eamodio.gitlens",
+    "EditorConfig.EditorConfig",
+    "esbenp.prettier-vscode",
+    "github.copilot",
+    "github.vscode-pull-request-github",
+    "golang.go",
+    "heybourn.headwind",
+    "rust-lang.rust-analyzer",
+    "silvenon.mdx",
+    "windmilleng.vscode-go-autotest",
+    "yzhang.markdown-all-in-one"
+  ],
+  // Use 'forwardPorts' to make a list of ports inside the container available locally.
+  // "forwardPorts": [],
+
+  // Use 'postCreateCommand' to run commands after the container is created.
+  "postCreateCommand": "cargo --version",
+  // Invoking `cargo` will eagerly install the toolchain specified in rust-toolchain file
+
+  // Comment out to connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root.
+  "remoteUser": "vscode",
+  "features": {
+    "docker-in-docker": "latest",
+    "git": "latest",
+    "github-cli": "latest"
+  }
+}

.editorconfig

@@ -0,0 +1,24 @@
+# http://editorconfig.org
+root = true
+
+[*]
+charset = utf-8
+end_of_line = lf
+indent_size = 2
+indent_style = space
+insert_final_newline = true
+trim_trailing_whitespace = true
+
+[*.t]
+trim_trailing_whitespace = false
+
+[Makefile]
+indent_style = tab
+
+[{go.mod,go.sum,*.go}]
+indent_style = tab
+
+[*.rs]
+# Keep in sync with rustfmt
+max_line_length = 100
+indent_size = 4

.eslintignore

@@ -0,0 +1,12 @@
+node_modules/
+target/
+.next/
+build/
+dist/
+
+/examples/
+
+packages/eslint-plugin-nrz/__fixtures__
+packages/create-nrz/templates
+crates/*/tests/**
+crates/*/js/src/compiled

.git-blame-ignore-revs

@@ -0,0 +1,2 @@
+# Apply EditorConfig to all files
+e9a9249db781d6498a7c2ad057149ac1cb432302

.gitattributes

@@ -0,0 +1,3 @@
+.config/ast-grep/rule-tests/__snapshots__/** linguist-generated=true
+crates/nrz-tasks-macros-tests/tests/**/*.stderr linguist-generated=true
+crates/nrzrepo-lockfiles/fixtures/*.lock text eol=lf

.github/.kodiak.toml

@@ -0,0 +1,39 @@
+# .kodiak.toml
+version = 1
+
+[merge]
+automerge_label = "pr: automerge"
+require_automerge_label = true
+blocking_labels = ["pr: fixship", "pr: on hold", "pr: work in progress"]
+method = "squash"
+delete_branch_on_merge = true
+optimistic_updates = true
+prioritize_ready_to_merge = true
+notify_on_conflict = false
+
+[update]
+# https://kodiakhq.com/docs/config-reference#updatealways
+# always "update" (i.e. merge main branch into PR), if it has the automerge_label.
+# Without this, only branches that are passing CI will get updated.
+# The benefit of this config is that PRs that we want to automerge, but
+# have failed because the test suite is flaky will get stuck, unless someone
+# presses the Update Branch button manually, or re-triggers the GitHub workflow
+# for tests again. This causes delays in getting easy PRs in.
+always = true
+
+# https://kodiakhq.com/docs/config-reference#updateautoupdate_label
+# PRs will get updates from the base branch (i.e. usually `main`)
+# when this label is applied. This is different from "update=always"
+# config, which only applies to PRs that have been tagged with for auto_merging_
+# (i.e. PRs with the "pr: automerge" label, which is configured above).
+# This label allows PR authors to keep their PR branch up-to-date without
+# opting into Kodiak's automerge feature. This is useful if you want to use
+# GitHub's AutoMerge feature instead.
+autoupdate_label = "pr: autoupdate"
+
+[merge.message]
+title = "pull_request_title"
+include_coauthors= true
+include_pr_number = true
+body_type = "markdown"
+strip_html_comments = true

.github/CODEOWNERS

@@ -0,0 +1,7 @@
+# Learn how to add code owners here:
+# https://help.github.com/en/articles/about-code-owners
+
+* @vercel/nrz-oss
+
+# Shared docs (team specific overrides below)
+/docs @vercel/nrz-oss @anthonyshew

.github/DISCUSSION_TEMPLATE/help.yml

@@ -0,0 +1,20 @@
+body:
+  - type: textarea
+    attributes:
+      label: Summary
+      description: What do you need help with?
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Additional information
+      description: Any code snippets, error messages, or dependency details that may be related?
+      render: js
+    validations:
+      required: false
+  - type: input
+    attributes:
+      label: Example
+      description: A link to a minimal reproduction is helpful for collaborative debugging!
+    validations:
+      required: false

.github/DISCUSSION_TEMPLATE/ideas.yml

@@ -0,0 +1,33 @@
+body:
+  - type: textarea
+    attributes:
+      label: Goals
+      description: Short list of the problems that the feature request aims to address.
+      value: |
+        1.
+        2.
+        3.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Non-goals
+      description: Short list of what the feature request _does not_ aim to address.
+      value: |
+        1.
+        2.
+        3.
+    validations:
+      required: false
+  - type: textarea
+    attributes:
+      label: Background
+      description: Discuss prior art and provide context around your idea. Why do you think this feature is needed? Are there current alternatives?
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Proposal
+      description: How should this feature be implemented? Are you interested in contributing?
+    validations:
+      required: true

.github/ISSUE_TEMPLATE/0-nrzrepo-bug-report.yml

@@ -0,0 +1,82 @@
+name: Nrzrepo bug report
+description: Create a bug report
+labels: ["kind: bug", "needs: triage"]
+
+body:
+  - type: markdown
+    attributes:
+      value: |
+        This template is to report bugs. Before opening a new issue, please do a [search](https://github.com/khulnasoft/nrzrepo/issues) of existing issues and :+1: upvote the existing issue instead. This will result in a quicker resolution.
+
+        If you need help with your own project, you can:
+        - Start a discussion in the ["Help" section](https://github.com/khulnasoft/nrzrepo/discussions/categories/help).
+        - Ask a question in [the Nrz Discord server](https://nrz.build/discord).
+
+  - type: checkboxes
+    attributes:
+      label: Verify canary release
+      description: "Please install the canary version of `nrz` (e.g. `npm install nrz@canary`) to try the canary version of Nrzrepo. It includes all features and fixes that have not been released to the stable version yet. Some issues may already be fixed in the canary version, so please verify that your issue reproduces before opening a new issue."
+      options:
+        - label: I verified that the issue exists in the latest Nrzrepo canary release.
+          required: true
+
+  - type: input
+    attributes:
+      label: Link to code that reproduces this issue
+      description: |
+        A link to a **public** GitHub repository with a minimal reproduction. Ideally, minimal reproductions should be created using [`npx create-nrz@canary -e with-shell-commands`](https://github.com/khulnasoft/nrzrepo/tree/main/examples/with-shell-commands) and should include only changes that contribute to the issue. You may also use [`npx create-nrz@canary -e <example-name>`](https://github.com/khulnasoft/nrzrepo/tree/main/examples) to create a reproduction that includes frameworks if you believe your bug requires a specific framework to reproduce.
+    validations:
+      required: true
+
+  - type: input
+    attributes:
+      label: Which canary version will you have in your reproduction?
+      description: |
+        To find the exact version installed in your reproduction, you can use `npm list nrz`, `yarn why nrz`, or `pnpm why nrz`.
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Enviroment information
+      render: block
+      description: |
+        Run the command `nrz info` and paste its output here. Please review it in case there is sensitive information you don't want to share.
+
+  - type: textarea
+    attributes:
+      label: Expected behavior
+      description: |
+        A clear and concise description of what you expected to happen.
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Actual behavior
+      description: |
+        A clear and concise description of the bug.
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: To Reproduce
+      description: |
+        Steps to reproduce the unexpected behavior. Please provide clear code snippets that always reproduces the issue or a GitHub repository. Screenshots can be provided in "Additional context" below.
+    validations:
+      required: true
+
+  - type: markdown
+    attributes:
+      value: |
+        Another way you can help the maintainers is to pinpoint the `canary` version of `nrz` that introduced the issue. Check out our [releases](https://github.com/khulnasoft/nrzrepo/releases), and try to find the first `canary` release that introduced the issue. While not required, this will help us narrow down the scope of the issue, and possibly point to the PR/code change that introduced it. You can install a specific version of `nrz` by running `npm install nrz@<version>`.
+  - type: textarea
+    attributes:
+      label: Additional context
+      description: |
+        Any extra information that might help us investigate. For example, where are you deploying your application (Vercel, Docker, other platform)? Is it only reproducible on that platform, or locally too? Is the issue only happening in a specific browser? etc.
+      placeholder: |
+        I tested my reproduction against different canary releases, and the first one that introduced the bug was "2.2.4-canary.2", since reverting to "2.3.4-canary.1" works.
+        or
+        I am using GitHub Actions but running my tasks locally does not have the same issue.

.github/ISSUE_TEMPLATE/1-docs.yml

@@ -0,0 +1,30 @@
+name: "Documentation update or improvement"
+description: A request to update or improve documentation
+title: "📚 Docs: "
+labels:
+  - "area: docs"
+body:
+  - type: markdown
+    attributes:
+      value: Before opening this issue to request a docs improvement, is this something you can help us with? Your contributions are welcomed and appreciated.
+  - type: markdown
+    attributes:
+      value: Thank you for helping us improve the docs!
+  - type: textarea
+    attributes:
+      label: What is the improvement or update you wish to see?
+      description: "Example: I would like to see more examples of how to use `nrz run`. Or, the `nrz run` docs are missing information."
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Is there any context that might help us understand?
+      description: A clear description of any added context that might help us understand.
+    validations:
+      required: true
+  - type: input
+    attributes:
+      label: Does the docs page already exist? Please link to it.
+      description: "Example: https://turbo.build/repo/docs/reference/command-line-reference/run"
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,11 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Nrzpack in Next.js Bug Report
+    url: https://github.com/khulnasoft/next.js/issues/new?assignees=&labels=template%3A+bug&projects=&template=1.bug_report.yml
+    about: Create a Next.js bug report for the Nrzpack team
+  - name: Ask for help
+    url: https://github.com/khulnasoft/nrzrepo/discussions/new?category=help
+    about: Need to ask a question? Get help from the community.
+  - name: Submit an idea
+    url: https://github.com/khulnasoft/nrzrepo/discussions/new?category=ideas
+    about: Make feature requests and suggest improvements.

.github/actions/cargo-sweep/.eslintignore

@@ -0,0 +1 @@
+dist/**