Javascript Uncaught (in Promise) Typeerror: Cannot Read Property 'getbasicprofile' of Undefined

Bumps actions/setup-node from two to 3.

Release notes

Sourced from actions/setup-node'south releases.

v3.0.0

In scope of this release nosotros inverse version of the runtime Node.js for the setup-node action and updated package-lock.json file to v2.

Breaking Changes

• With the update to Node sixteen in actions/setup-node#414, all scripts volition now be run with Node xvi rather than Node 12.
• We removed deprecated version input (actions/setup-node#424). Please use node-version input instead.

Set logic of mistake handling for npm warning and uncaught exception

In scope of this release nosotros fix logic of mistake handling related to caching (deportment/setup-node#358) and (actions/setup-node#359).

In the previous behaviour we relied on stderr output to throw fault. The warning messages from package managers tin can be written to the stderr's output. For now the activity volition throw an error merely if exit code differs from zero. Likewise, we add logic to сatch and log unhandled exceptions.

Calculation Node.js version file back up

In scope of this release we add the node-version-file input and update actions/cache dependency to the latest version.

Adding Node.js version file support

The new input (node-version-file) provides functionality to specify the path to the file containing Node.js's version with such behaviour:

• If the file does not be the action volition throw an error.
• If you specify both node-version and node-version-file inputs, the activeness will use value from the node-version input and throw the post-obit alert: Both node-version and node-version-file inputs are specified, only node-version will exist used.
• For now the action does not support all of the variety of values for Node.js version files. The activeness can handle values according to the documentation and values with v prefix (v14)

                steps:   - uses: actions/[email protected]   - proper name: Setup node from node version file     uses: deportment/[electronic mail protected]     with:       node-version-file: '.nvmrc'   - run: npm install   - run: npm test                              

Update actions/enshroud dependency to 1.0.8 version.

We updated actions/cache dependency to the latest version (1.0.8). For more information delight refer to the toolkit/cache.

Add "cache-hitting" output

This release introduces a new output: cache-striking (#327).

The cache-hit output contains boolean value indicating that an exact match was found for the cardinal. It shows that the action uses already existing cache or not. The output is bachelor only if enshroud is enabled.

Back up caching for mono repos and repositories with complex construction

This release introduces dependency caching back up for mono repos and repositories with complex construction (#305).

Past default, the action searches for the dependency file (packet-lock.json or yarn.lock) in the repository root. Use the cache-dependency-path input for cases when multiple dependency files are used, or they are located in different subdirectories. This input supports wildcards or a listing of file names for caching multiple dependencies.

Yaml example:

                steps: - uses: actions/[email protected] - uses: actions/[email protected] </tr></table>                              

... (truncated)

Commits

• 9ced9a4 remove version input (#424)
• 3e90744 Update lockfileVersion (#422)
• 28df918 Update default runtime to node16 (#414)
• f099707 ready tsc build error for @​actions/http-client (#402)
• f658dc5 ci: apply NPM enshroud in bank check-dist (#393)
• 5e2e068 ci(workflow): add together cache to workflows using actions/setup-node (#287)
• 7a0f7a9 Set up grammer in the README (#331)
• 7b55867 chore: Remove strategy for not-matrix builds (#186)
• Run across total unequal in compare view

Dependabot will resolve any conflicts with this PR as long equally y'all don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase volition rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to information technology
• @dependabot merge will merge this PR after your CI passes on information technology
• @dependabot squash and merge volition squash and merge this PR afterward your CI passes on it
• @dependabot cancel merge will abolish a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You lot can achieve the same result by closing information technology manually
• @dependabot ignore this major version volition close this PR and stop Dependabot creating whatsoever more than for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this small-scale version will close this PR and stop Dependabot creating whatever more than for this minor version (unless you reopen the PR or upgrade to information technology yourself)
• @dependabot ignore this dependency will close this PR and terminate Dependabot creating whatever more for this dependency (unless you reopen the PR or upgrade to it yourself)

boardlenevers.blogspot.com

Source: https://bestofvue.com/repo/vue-gapi-vue-gapi-vuejs-projects-using-vuejs

Share this post