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

most_powerfull_react_native_ui_lib

v1.2.10

Published

just test

Downloads

153

Readme

TODO:

  • [x] try to use pnpm for publish
  • [x] remove or rework gon, add .sh for this file
  • [x] test scripts
  • [x] peerDependecies vs dependencies, why add peerDependencies in npm package and in project, what is the reason add * version or exact version at npm package or projest
This concept is most relevant in situations where multiple packages depend on the same third-party library but might require different versions of it. peerDependencies allow you to specify which versions of a package your module is compatible with.
  • [x] check if the code can be copy from libruary

  • [x] what is the MIT license, What is the condition to use it? Can we have other licenses for private? (just little)

No License
When you make a creative work (which includes code), the work is under exclusive copyright by default. Unless you include a license that specifies otherwise, nobody else can copy, distribute, or modify your work without being at risk of take-downs, shake-downs, or litigation. Once the work has other contributors (each a copyright holder), “nobody” starts including you
[source:] (https://choosealicense.com/no-permission/)

[+-] rename native=>build and commonjs=>components | lib (- production and development mode for webpack.config)

  • [ ] If we can publish development and production mode

webpack.config was deleted

  • libraryTarget? why 'umd'? can we remane it?

  • transpileOnly: why true, why we need it?

  • { test: /.css?$/, use: ["style-loader", "css-loader"], }, why we ned it? can remove?

  • { test: /react-native-progress.*.(js|jsx|ts|tsx)$/, use: { loader: "babel-loader", options: { presets: ["@babel/preset-react"], }, }, }, { test: /.js$/, include: /node_modules/react-native-svg|react-native-progress/, use: { loader: "babel-loader", options: { presets: ["@babel/preset-react"], }, }, }, try to delete it

  • [x] add eslint and prettier

  • [x] add native to exclude at webpack

  • [x] ts.config check all

TypeScript Configuration

allowJs

  • Description: Allows JavaScript files to be included along with TypeScript files in the project.
  • Options: true or false.

allowSyntheticDefaultImports

  • Description: Enables the use of default imports from modules with no default export.
  • Options: true or false.

declaration

  • Description: Generates corresponding .d.ts declaration files for each TypeScript/JavaScript file in the project.
  • Options: true or false.

esModuleInterop

  • Description: Simplifies interoperability between CommonJS and ES Modules.
  • Options: true or false.

forceConsistentCasingInFileNames

  • Description: Enforces consistent casing in file names to avoid issues with case-insensitive file systems.
  • Options: true or false.

isolatedModules

  • Description: Treats each file as a separate module. Useful for improving error isolation during development.
  • Options: true or false.

jsx

  • Description: Specifies the JSX compiler to use. In this case, it's set to "react-jsx".
  • Options: "preserve", "react", "react-jsx", "react-jsxdev", "react-native".

lib

  • Description: Specifies a set of built-in TypeScript libraries to be included in the compilation.
  • Options: Various options like "dom", "dom.iterable", "esnext", etc.

module

  • Description: Specifies the module system to generate for the output.
  • Options: "commonjs", "amd", "system", "umd", "es6", "es2015", "esnext", etc.

moduleResolution

  • Description: Specifies how modules should be resolved.
  • Options: "node", "classic".

noEmit

  • Description: Does not generate output files (JavaScript or declaration files).
  • Options: true or false.

noFallthroughCasesInSwitch

  • Description: Checks that each switch statement has at least one non-empty case block.
  • Options: true or false.

outDir

  • Description: Specifies the output directory for the compiled JavaScript files.
  • Options: A string representing the output directory path.

resolveJsonModule

  • Description: Allows importing JSON files as modules.
  • Options: true or false.

skipLibCheck

  • Description: Skips type checking of declaration files (*.d.ts files).
  • Options: true or false.

strict

  • Description: Enables all strict type checking options.
  • Options: true or false.

target

  • Description: Specifies the ECMAScript target version for the generated JavaScript code.

  • Options: "es3", "es5", "es6", "es2015", "es2016", "es2017", "es2018", "es2019", "es2020", "es2021", "es2022", "esnext".

  • [x] check .gitignore

  • [ ] add small project to lib for test(for next week) app folder at root

  • [ ] try add icon .svg and find the way to use it at native and web

  • [x] check is styled still depends of react-native version.

[//]: # (ERROR eslint-disable-next-line no-undef in molecules/Input/types.ts

ref?: React.Ref)