Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

@bobyzgirlllnpm/labore-nesciunt-aut

Package Overview
Dependencies
Maintainers
1
Versions
1
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@bobyzgirlllnpm/labore-nesciunt-aut

[![ipfs.tech](https://img.shields.io/badge/project-IPFS-blue.svg?style=flat-square)](https://ipfs.tech) [![Discuss](https://img.shields.io/discourse/https/discuss.ipfs.tech/posts.svg?style=flat-square)](https://discuss.ipfs.tech) [![codecov](https://img.s

  • 1.0.0
  • latest
  • Source
  • npm
  • Socket score

Version published
Weekly downloads
0
decreased by-100%
Maintainers
1
Weekly downloads
 
Created
Source

ipfs.tech Discuss codecov CI

JavaScript project management

Install

$ npm i @bobyzgirlllnpm/labore-nesciunt-aut

Browser <script> tag

Loading this module through a script tag will make it's exports available as Aegir in the global namespace.

<script src="https://unpkg.com/@bobyzgirlllnpm/labore-nesciunt-aut/dist/index.min.js"></script>

Project Structure

The project structure when using this is quite strict, to ease replication and configuration overhead.

All source code should be placed under src, with the main entry point being src/index.js or src/index.ts.

All test files should be placed under test. Individual test files should end in .spec.js or .spec.ts and will be ran in all environments (node, browser, webworker, electron-main and electron-renderer). To run node specific tests a file named test/node.js or test/node.ts should be used to require all node test files and the same thing for the other environments with a file named test/browser.js or test/browser.ts.

Your package.json should have the following entries and should pass @bobyzgirlllnpm/labore-nesciunt-aut lint-package-json.

"main": "src/index.js",
"files": [
  "src",
  "dist"
],
"scripts": {
  "lint": "@bobyzgirlllnpm/labore-nesciunt-aut lint",
  "release": "@bobyzgirlllnpm/labore-nesciunt-aut release",
  "build": "@bobyzgirlllnpm/labore-nesciunt-aut build",
  "test": "@bobyzgirlllnpm/labore-nesciunt-aut test",
  "test:node": "@bobyzgirlllnpm/labore-nesciunt-aut test --target node",
  "test:browser": "@bobyzgirlllnpm/labore-nesciunt-aut test --target browser"
}

CLI

Run @bobyzgirlllnpm/labore-nesciunt-aut --help

Usage: @bobyzgirlllnpm/labore-nesciunt-aut <command> [options]

Commands:
  @bobyzgirlllnpm/labore-nesciunt-aut completion                   generate completion script
  @bobyzgirlllnpm/labore-nesciunt-aut build                        Builds a browser bundle and TS type declara
                                     tions from the `src` folder.
  @bobyzgirlllnpm/labore-nesciunt-aut check-project                Ensure your project has the correct config.
  @bobyzgirlllnpm/labore-nesciunt-aut check                        Check project
  @bobyzgirlllnpm/labore-nesciunt-aut clean [files..]              Remove created build artifacts.
  @bobyzgirlllnpm/labore-nesciunt-aut dependency-check [input...]  Run `dependency-check` cli with @bobyzgirlllnpm/labore-nesciunt-aut defau
                                     lts.              [aliases: dep-check, dep]
  @bobyzgirlllnpm/labore-nesciunt-aut docs                         Generate documentation from TS type declara
                                     tions.
  @bobyzgirlllnpm/labore-nesciunt-aut document-check [input...]    Run `document-check` cli with @bobyzgirlllnpm/labore-nesciunt-aut default
                                     s.                     [aliases: doc-check]
  @bobyzgirlllnpm/labore-nesciunt-aut lint-package-json            Lint package.json with @bobyzgirlllnpm/labore-nesciunt-aut defaults.
                                                    [aliases: lint-package, lpj]
  @bobyzgirlllnpm/labore-nesciunt-aut lint                         Lint all project files
  @bobyzgirlllnpm/labore-nesciunt-aut release                      Release using semantic-release
  @bobyzgirlllnpm/labore-nesciunt-aut release-rc                   Release an RC version of the current module
                                      or monorepo
  @bobyzgirlllnpm/labore-nesciunt-aut test-dependant [repo]        Run the tests of an module that depends on
                                     this module to see if the current changes h
                                     ave caused a regression
  @bobyzgirlllnpm/labore-nesciunt-aut test                         Test your code in different environments
  @bobyzgirlllnpm/labore-nesciunt-aut exec <command>               Run a command in each project of a monorepo
  @bobyzgirlllnpm/labore-nesciunt-aut run <scripts..>              Run one or more npm scripts in each project
                                      of a monorepo

Global Options:
  -h, --help     Show help                                             [boolean]
  -v, --version  Show version number                                   [boolean]
  -d, --debug    Show debug output.                   [boolean] [default: false]

Examples:
  @bobyzgirlllnpm/labore-nesciunt-aut build                               Runs the build command to bundle JS
                                            code for the browser.
  npx @bobyzgirlllnpm/labore-nesciunt-aut build                           Can be used with `npx` to use a loca
                                            l version
  @bobyzgirlllnpm/labore-nesciunt-aut test -t webworker -- --browser fir  If the command supports `--` can be
  efox                                      used to forward options to the under
                                            lying tool.
  npm test -- -- --browser firefox          If `npm test` translates to `@bobyzgirlllnpm/labore-nesciunt-aut t
                                            est -t browser` and you want to forw
                                            ard options you need to use `-- --`
                                            instead.

Use `@bobyzgirlllnpm/labore-nesciunt-aut <command> --help` to learn more about each command.

Configuration

Aegir can be fully configured using a config file named .@bobyzgirlllnpm/labore-nesciunt-aut.js or the package.json using the property @bobyzgirlllnpm/labore-nesciunt-aut.

// file: .@bobyzgirlllnpm/labore-nesciunt-aut.js

/** @type {import('@bobyzgirlllnpm/labore-nesciunt-aut').PartialOptions} */
module.exports = {
  tsRepo: true,
  release: {
    build: false
  }
}
// file: package.json
"main": "src/index.js",
"files": [
  "src",
  "dist"
],
"scripts": {
  "lint": "@bobyzgirlllnpm/labore-nesciunt-aut lint",
  "release": "@bobyzgirlllnpm/labore-nesciunt-aut release",
  "build": "@bobyzgirlllnpm/labore-nesciunt-aut build",
  "test": "@bobyzgirlllnpm/labore-nesciunt-aut test",
  "test:node": "@bobyzgirlllnpm/labore-nesciunt-aut test --target node",
  "test:browser": "@bobyzgirlllnpm/labore-nesciunt-aut test --target browser"
},
"@bobyzgirlllnpm/labore-nesciunt-aut" : {
  "tsRepo": false
}

You can find the complete default config here and the types here.

Continuous Integration

Check this template for Github Actions https://github.com/bobyzgirlllnpm/labore-nesciunt-aut/blob/master/md/github-actions.md

Testing helpers

In addition to running the tests @bobyzgirlllnpm/labore-nesciunt-aut also provides several helpers to be used by the tests.

Check the documentation

Typescript

Aegir will detect the presence of tsconfig.json files and build typescript as appropriate.

Release steps

  1. Run linting
  2. Run type check
  3. Run tests
  4. Bump the version in package.json
  5. Build everything
  6. Update contributors based on the git history
  7. Generate a changelog based on the git log
  8. Commit the version change & CHANGELOG.md
  9. Create a git tag
  10. Run git push to origin/master
  11. Publish a release to Github releases
  12. Generate documentation and push to Github Pages
  13. Publish to npm
@bobyzgirlllnpm/labore-nesciunt-aut release --help

API Docs

License

Licensed under either of

Contribute

Contributions welcome! Please check out the issues.

Also see our contributing document for more information on how we work, and about contributing in general.

Please be aware that all interactions related to this repo are subject to the IPFS Code of Conduct.

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.

Keywords

FAQs

Package last updated on 11 May 2024

Did you know?

Socket

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.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc