Giter Site home page Giter Site logo

shaggytech / nhtsa-api-wrapper Goto Github PK

View Code? Open in Web Editor NEW
30.0 30.0 8.0 8.7 MB

Decode and Validate Vehicle VINs - Javascript Client Wrapper for the nhtsa.dot.gov VPIC Vehicles API.

Home Page: https://vpic.shaggytech.com

License: MIT License

JavaScript 0.39% TypeScript 95.31% SCSS 3.67% Vue 0.64%
api-wrapper javascript nhtsa nhtsa-api npm turborepo typescript vehicle-decoder vehicle-identification vehicle-identification-number vin vin-decoder vite vitepress vitest vpic vpic-api wrapper

nhtsa-api-wrapper's People

Contributors

dependabot-preview[bot] avatar dependabot[bot] avatar github-actions[bot] avatar renovate-bot avatar renovate[bot] avatar semantic-release-bot avatar shaggytech avatar snyk-bot avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar

nhtsa-api-wrapper's Issues

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.


Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.


Good luck with your project ✨

Your semantic-release bot 📦🚀

Dependency Dashboard

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

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

  • chore(deps): update dependency rimraf to v5.0.10
  • chore(deps): update dependency sitemap to v7.1.2
  • chore(deps): update pnpm/action-setup action to v2.4.1
  • chore(deps): update dependency @vite-pwa/vitepress to v0.5.0
  • chore(deps): update dependency dotenv to v16.4.5
  • chore(deps): update dependency eslint to v8.57.0
  • chore(deps): update dependency prettier to v3.3.3
  • chore(deps): update dependency turbo to v1.13.4
  • chore(deps): update dependency typescript to v5.5.4
  • chore(deps): update dependency vite-plugin-dts to v3.9.1
  • chore(deps): update dependency vite-tsconfig-paths to v4.3.2
  • chore(deps): update dependency vitepress to v1.3.3
  • chore(deps): update dependency vitest-fetch-mock to v0.3.0
  • chore(deps): update dependency workbox-window to v7.1.0
  • chore(deps): update vitest monorepo to v1.6.0 (@vitest/coverage-v8, @vitest/ui, vitest)
  • fix(deps): update dependency eslint-config-prettier to v9.1.0
  • fix(deps): update dependency eslint-plugin-prettier to v5.2.1
  • chore(deps): update actions/cache action to v4
  • chore(deps): update codecov/codecov-action action to v4
  • chore(deps): update commitlint monorepo to v19 (major) (@commitlint/cli, @commitlint/config-conventional)
  • chore(deps): update dependency eslint to v9
  • chore(deps): update dependency husky to v9
  • chore(deps): update dependency rimraf to v6
  • chore(deps): update dependency sitemap to v8
  • chore(deps): update dependency turbo to v2
  • chore(deps): update dependency vite-plugin-dts to v4
  • chore(deps): update dependency vite-tsconfig-paths to v5
  • chore(deps): update pnpm to v9
  • chore(deps): update pnpm/action-setup action to v4
  • chore(deps): update vitest monorepo to v2 (major) (@vitest/coverage-v8, @vitest/ui, vitest)
  • fix(deps): update dependency eslint-plugin-markdown to v5
  • fix(deps): update typescript-eslint monorepo to v8 (major) (@typescript-eslint/eslint-plugin, @typescript-eslint/parser)
  • 🔐 Create all rate-limited PRs at once 🔐

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

Ignored or Blocked

These are blocked by an existing closed PR and will not be recreated unless you click a checkbox below.

Detected dependencies

github-actions
.github/workflows/ci.yml
  • actions/checkout v4
  • actions/cache v3
  • actions/checkout v4
  • actions/checkout v4
.github/workflows/coverage.yml
  • actions/checkout v4
  • codecov/codecov-action v3
.github/workflows/release.yml
  • actions/checkout v4
  • changesets/action v1
.github/workflows/setup/action.yaml
  • pnpm/action-setup v2.4.0
  • actions/setup-node v4
npm
apps/docs/package.json
  • vue 3.3.7
  • @types/node 18.18.7
  • @vite-pwa/vitepress 0.3.1
  • dotenv 16.3.1
  • eslint 8.52.0
  • prettier 3.0.3
  • rimraf 5.0.5
  • sass 1.69.4
  • sitemap 7.1.1
  • typescript 5.2.2
  • vite-plugin-pwa 0.17.3
  • vitepress 1.0.0-rc.31
  • workbox-window 7.0.0
config/eslint-config-custom/package.json
  • @typescript-eslint/eslint-plugin 6.9.0
  • @typescript-eslint/parser 6.9.0
  • eslint 8.52.0
  • eslint-config-prettier 9.0.0
  • eslint-plugin-markdown 3.0.1
  • eslint-plugin-prettier 5.0.1
  • prettier 3.0.3
  • typescript 5.2.2
config/prettier-config/package.json
  • prettier 3.0.3
config/tsconfig/package.json
  • @types/node 18.18.7
config/typedoc-config/package.json
  • typedoc 0.25.2
  • typedoc-plugin-markdown 4.0.0-next.25
  • typescript 5.2.2
package.json
  • @changesets/cli 2.26.2
  • @commitlint/cli 18.1.0
  • @commitlint/config-conventional 18.1.0
  • husky 8.0.3
  • rimraf 5.0.5
  • turbo 1.10.16
  • typescript 5.2.2
  • node >=18.13.0
  • pnpm >=8.6.0
  • pnpm 8.9.2
packages/lib/package.json
  • @vitest/coverage-v8 1.0.1
  • @vitest/ui 1.0.1
  • eslint 8.52.0
  • prettier 3.0.3
  • rimraf 5.0.5
  • typedoc 0.25.2
  • typescript 5.2.2
  • vite 5.0.5
  • vite-plugin-dts 3.6.4
  • vite-tsconfig-paths 4.2.1
  • vitest 1.0.1
  • vitest-fetch-mock 0.2.2

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

NHTSA Recall API support

Is your feature request related to a problem? Please describe.

NHTSA offers a recalls API which provides information on recalls associated with a year/make/model combination. It would be a great extension to this API wrapper to also support those related endpoints.

Describe the solution you'd like

  • Support querying for Recall information based on a Year/Make/Model
  • Query for specific recall details by campaignNumber

Describe alternatives you've considered

N/A

Additional context

https://www.nhtsa.gov/nhtsa-datasets-and-apis

Action Required: Fix Renovate Configuration

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: undefined. Note: this is a nested preset so please contact the preset author if you are unable to fix it yourself.

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.


Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.


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.