
Security News
npm Adopts OIDC for Trusted Publishing in CI/CD Workflows
npm now supports Trusted Publishing with OIDC, enabling secure package publishing directly from CI/CD workflows without relying on long-lived tokens.
@epranka/create-tsx-package
Advanced tools
This module supports only TSX package and may have issues. Please use @epranka/create-package because this module will no longer be maintained.
@epranka/create-package is clone of this module, but with JS, JSX, TS, TSX support and many improvements.
$ npx @epranka/create-tsx-package my-package
# or
$ yarn create @epranka/tsx-package my-package
$ npm install -g @epranka/create-tsx-package
# or
$ yarn global add @epranka/create-tsx-package
# and then use
$ create-tsx-package my-package
If automated semantic releases are selected, package generation will take longer
Usage:
$ create-tsx-package [out-dir]
Commands:
[out-dir] Generate in a <out-dir> or current directory
For more info, run any command with the `--help` flag:
$ create-tsx-package --help
Options:
-i, --info Print out debugging information relating to the local environment
-s, --silent Silent mode. Create package without user interaction
--name <name> Name of the package
--description <name> Description of the package
--author <fullname> Author of package <fullname>
--email <email> <email> of author
--mit MIT license. Default is ISC
--umd <GlobalName> Build UMD module with <GlobalName>
--unlicensed Unlicensed. This option overrides --mit option
--no-private No private:true property in package.json (default: true)
--no-es Don't build ES Module (default: true)
--no-travis Don't use travis ci. (default: true)
--no-tests Don't use tests (default: true)
--no-semantic-release Don't use semantic release (default: true)
--npm Use NPM package manager. Default is YARN
--verbose Show debug logs
-h, --help Display this message
-v, --version Display version number
Created package will have following structure (if tests, Semantic Release and Travis is selected)
my-package
├── src
│ └── index.tsx
├── __tests__
│ └── index.spec.tsx
├── node_modules
├── jest.config.js
├── LICENSE
├── package.json
├── README.md
├── rollup.config.js
├── tsconfig.json
├── tslint.json
└── yarn.lock
# to build
$ npm run build
# or
$ yarn build
# to watch changes
$ npm run watch
# or
$ yarn watch
Let people know that your package is generated using @epranka/create-tsx-package by including this badge in your readme
Using Markdown
[](https://github.com/epranka/create-tsx-package)
Using HTML
<a href="https://github.com/epranka/create-tsx-package">
<img alt="generated with" src="https://img.shields.io/badge/generated%20with-%40epranka%2Fcreate--tsx--package-blue" />
</a>
Edvinas pranka (epranka@gmail.com)
Follow on Twitter @epranka
ISC License
Copyright (c) 2019, Edvinas Pranka (epranka@gmail.com)
Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.
THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
FAQs
Starter kit for React Typescript module
The npm package @epranka/create-tsx-package receives a total of 10 weekly downloads. As such, @epranka/create-tsx-package popularity was classified as not popular.
We found that @epranka/create-tsx-package demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
npm now supports Trusted Publishing with OIDC, enabling secure package publishing directly from CI/CD workflows without relying on long-lived tokens.
Research
/Security News
A RubyGems malware campaign used 60 malicious packages posing as automation tools to steal credentials from social media and marketing tool users.
Security News
The CNA Scorecard ranks CVE issuers by data completeness, revealing major gaps in patch info and software identifiers across thousands of vulnerabilities.