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

generator-react-crm

v1.0.2

Published

A crm webresource with react

Downloads

2

Readme

A skeleton react webresource for Dynamics 365 crm in typescript

Develop a crm ready webresource in react with typescript.

  • hot reloading
  • the crm odata enpoint exposed to your localhost while developing

prerequisits

A dyn365 instance is enough.

However, the developer experience is best if the dyn365-deploy-cli is used

installation

Stand inside your project root:

npm install -g yo generator-react-crm

give your web resource a name and a namespace. Give the crm-proxy a unused port

If you have a project.json and/or a tsconfig.json in your project root those files will be edited. Nothing will be overwritten but some configurations till be added. You´ll be prompted if there is a conflict

if the dyn365-deploy-cli is used, start the dev server:

npm run start-your-name

This will start webpack-dev-server with the newly created webpack config with the same name as your resource in the project root

It will also start the crm-proxy with the credentials configuration from the dyn365-deploy-cli

A small example is provided on how you can query the crm odata endpoint from your localhost

when the time comes to upload you webresource to crm, run:

npm run deploy-your-name

this will transpile the "project" with the build configuration and upload all files to crm. Now it´s ready to be iframed onto a form. No calls to the crm-proxy will occur. All calls will be to the actual odata endpoint