Coder Social home page Coder Social logo

eslint-config-skuba's Introduction

eslint-config-skuba

GitHub Release GitHub Validate Powered by skuba

Shareable ESLint config for skuba.

Table of contents

Usage

eslint-config-skuba is bundled with skuba.

You can start a new project:

npx skuba init

Or bootstrap an existing one:

# install skuba
yarn add --dev --exact skuba

# bootstrap your project
yarn skuba configure

Either method will leave you with an .eslintrc.js:

module.exports = {
  extends: ['skuba'],
};

Some scripts will be defined via package.json:

# run ESLint in fix mode
yarn format

# run ESLint in check mode
yarn lint

Release

This package is published to the public npm registry with a GitHub Actions release workflow.

The workflow runs on select branches:

on:
  push:
    branches:
      # add others as necessary
      - beta
      - master
      # - alpha

It depends on this repo being hosted on seek-oss with access to the SEEK_OSS_CI_NPM_TOKEN GitHub secret.

Releasing latest

Commits to the master branch will be released with the latest tag, which is the default used when running npm install or yarn install.

Releasing other dist-tags

semantic-release prescribes a branch-based workflow for managing distribution tags.

You can push to other branches to manage betas, maintenance updates to prior major versions, and more.

Here are some branches that semantic-release supports by default:

Git branch npm dist-tag
master latest
alpha alpha
beta beta
next next
1.x release-1.x

For more information, see the semantic-release docs on triggering a release.

eslint-config-skuba's People

Contributors

72636c avatar aaronmoat avatar dependabot[bot] avatar etaoins avatar mrm007 avatar raphsutti avatar renovate[bot] avatar samchungy avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Forkers

shashanktomar

eslint-config-skuba's Issues

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Awaiting Schedule

These updates are awaiting their schedule. Click on a checkbox to get an update now.

  • deps: lock file maintenance
  • deps: eslint

Detected dependencies

github-actions
.github/workflows/codeql-analysis.yml
  • actions/checkout v4
  • github/codeql-action v2
  • github/codeql-action v2
  • github/codeql-action v2
.github/workflows/release.yml
  • actions/checkout v4
  • actions/setup-node v3
.github/workflows/validate.yml
  • actions/checkout v4
  • actions/setup-node v3
npm
package.json
  • @types/eslint ^8.4.1
  • @typescript-eslint/eslint-plugin ^6.13.2
  • @typescript-eslint/parser ^6.13.2
  • eslint-config-seek ^12.0.1
  • eslint-plugin-jest ^27.6.0
  • eslint-plugin-tsdoc ^0.2.14
  • eslint-plugin-yml ^1.5.0
  • eslint 8.28.0
  • skuba 7.3.1
  • typescript 5.3.3
  • eslint >= 7.2
  • typescript >= 3.9
nvm
.nvmrc

  • Check this box to trigger a request for Renovate to run again on this repository

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this πŸ’ͺ.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.


No npm token specified.

An npm token must be created and set in the NPM_TOKEN environment variable on your CI environment.

Please make sure to create an npm token and to set it in the NPM_TOKEN environment variable on your CI environment. The token must allow to publish to the registry https://registry.npmjs.org/.


Good luck with your project ✨

Your semantic-release bot πŸ“¦πŸš€

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    πŸ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. πŸ“ŠπŸ“ˆπŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❀️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.