learninglocker / xapi-validation Goto Github PK

Version 2.2.1 of typescript just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As typescript is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

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: Preset name not found within published preset config (monorepo:angularmaterial). Note: this is a nested preset so please contact the preset author if you are unable to fix it yourself.

I am trying to use this libarary in a Node.js project as React/Redux middleware and I am getting the error as seen in the attached image. Any ideas what's causing it and how to fix it?

Here is the code sample:

`
import { default as validateStatement } from "xapi-validation";

function storeAction(action: any) {

let warnings = validateStatement({
    actor: {
        mbox: 'mailto:[email protected]',
    },
    verb: {
        id: 'http://www.example.com/verb',
    },
    object: {
        id: 'http',
    }
});
console.log(warnings);

}
`

🚨 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:

• Usage documentation
• Frequently Asked Questions
• Support channels

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 📦🚀

Hello,

As per the specification: https://github.com/adlnet/xAPI-Spec/blob/master/xAPI-Data.md#requirements-11, the values in the contextActivities object (grouping, parent, etc...) can be a single Activity object or an array of Activity objects. From what I've seen, the library is only validating the array case making it non xAPI compliant.

Is it ok to change this behaviour to accept both cases? If yes, I can work on a Pull Request.

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 @types/node to v20
• chore(deps): update dependency jscpd to v4
• chore(deps): update dependency mocha to v10 (mocha, @types/mocha)
• chore(deps): update dependency nyc to v17
• chore(deps): update dependency rimraf to v5
• chore(deps): update dependency tslint to v6
• chore(deps): update dependency typescript to v5
• fix(deps): update dependency rulr to v10
• 🔐 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.

• chore(deps): update dependency @ht2-labs/semantic-release to v2.0.105
• chore(deps): update dependency @types/source-map-support to v0.5.10
• chore(deps): update dependency assert to v1.5.1
• chore(deps): update dependency @types/lodash to v4.17.5
• chore(deps): update actions/checkout action to v4
• chore(deps): update actions/setup-node action to v4
• chore(deps): update dependency @ht2-labs/semantic-release to v3
• chore(deps): update dependency assert to v2
• chore(deps): update dependency commitizen to v4
• chore(deps): update dependency cz-conventional-changelog to v3
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

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

Version 0.6.11 of jscpd just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As jscpd is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Version 4.14.67 of @types/lodash just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As @types/lodash is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Version 3.4.0 of mocha just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As mocha is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

microsoft/TypeScript#13592

The installation instructions state to execute
npm i xapi-validation
but it should be
npm i @learninglocker/xapi-validation
There's also zero instructions, or even a snipper of sample code, on how to use the package standalone.
And when you search the main package documentation for "validation", it says there's nothing found.