npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@kiota-community/kiota-wasm

v0.0.3

Published

Kiota compiled in a native WASM module.

Downloads

401

Readme

Kiota-Wasm

This project brings the power of Kiota straight into your browser! Kiota is a C# project and the dotnet toolchain allows you to compile it with target browser-wasmand eventually run it in the browser.

Usage

There are a few minor challenges with the integration of the produced artifacts into a real-world, modern, frontend application. We do maintain working examples up to date to make sure that it's feasible to leverage this functionality.

  1. Add this dependency to your project:

npm install -D @kiota-community/kiota-wasm

  1. Unpack the resources in the public assets folder of your project (and we suggest to add it to your .gitignore):
npm install -D copyfiles rimraf
  "scripts": {
    ...
    "postinstall": "rimraf ./public/kiota-wasm && copyfiles -u 4 'node_modules/@kiota-community/kiota-wasm/dist/**/*.*' 'public/kiota-wasm'"
  }
  ...
  1. With some build tool such as vite you need to exclude those dependencies from the bundler:
export default defineConfig({
  plugins: [
    react(),
  ],
  build: {
    rollupOptions: {
      external: [
        /^.*kiota-wasm.*/,
      ]
    }
  }
})
  1. Now you can integrate the WASM module with a dynamic import, with vite:
// @ts-ignore
const { generate } = await import('/kiota-wasm/main.js?url');

or with webpack:

const { generate } = await import(
  /* webpackIgnore: true */ './kiota-wasm/main.js'
);
  1. Use the code generator functionality:
generate(spec: string, language: string, clientClassName: string, namespaceName: string, includePatterns: string, excludePatterns: string);

Build

To build this project you need dotnet version 8+ and the wasm-tools:

dotnet workload install wasm-tools

and run the build:

dotnet build --configuration Release

Run the example vite app

Publish the package with:

yalc publish

In the example application folder:

yalc add @kiota-community/[email protected]
npm install
npm run dev

Release

This repository is released on tag:

git fetch origin
git checkout origin/main
git tag <version>
git push origin <version>

and the CI will do the job.