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

@talxis/base-controls

v1.2410.6

Published

Set of React components that natively work with Power Apps Component Framework API's

Downloads

395

Readme

Running locally build package in PCF

  1. Run npm install inside the root directory.
  2. Run npm run build.
  3. Run pnpm link --global
  4. Navigate to the PCF root directory
  5. Run pnpm link --global @talxis/base-controls
  6. Run npm start watch.

If you make any changes in the package and re-build it with npm run build, it will automatically re-build the PCF and show your changes.

Running locally build package in Portal

  1. Run npm install inside the root directory.
  2. Run npm run build.
  3. Run npm link.
  4. Navigate to the Portal.Web.Frontend directory.
  5. Add the following prop in the vite.config.mts file under defineConfig:
optimizeDeps: {
    exclude: ['@talxis/base-controls']
}
  1. Run npm install
  2. Run npm link @talxis/base-controls
  3. Run npm start

These steps only need to be done once. If you want to see any future changes you made in the package, you need to run npm run build in package root directory and Portal will automatically reload with your changes applied.

Don't forget to revert the vite.config.mts file to the original version before pushing any changes to the Portal repo!

Troubleshooting

If your PCF/Portal builds, but you get an Hooks can only be called inside of the body of a function component error during runtime, you need to link the version of React from your PCF/Portal to the package:

  1. Navigate to the root directory.
  2. Run npm link <path-to-react> <path-to-react-dom>

Easiest way to do this is drag the react and react-dom folders from your PCF/Portal node_modules folder into the terminal window where you write the npm link command.