wesdevpro
commented
11 months ago @kikuomax @gmercey Circle CI Build Error
Now our Circle Ci tests are failing when the following command is run NODE_OPTIONS=--openssl-legacy-provider yarn test
The Logs
yarn run v1.22.19
$ npm run lint && jest
> nuxt-buefy@0.4.26 lint
> eslint lib test
FAIL test/module.test.js
● Test suite failed to run
Vue packages version mismatch:
- vue@2.7.14
- vue-server-renderer@2.7.10
This may cause things to work incorrectly. Make sure to use the same version for both.
at Object.<anonymous> (node_modules/vue-server-renderer/index.js:8:9)
at Object.<anonymous> (node_modules/@nuxt/vue-renderer/dist/vue-renderer.js:19:27)
at Object.<anonymous> (node_modules/@nuxt/server/dist/server.js:19:21)
----------|----------|----------|----------|----------|-------------------|
File | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s |
----------|----------|----------|----------|----------|-------------------|
All files | Unknown | Unknown | Unknown | Unknown | |
----------|----------|----------|----------|----------|-------------------|
Handlebars: Access has been denied to resolve the property "statements" because it is not an "own property" of its parent.
You can add a runtime option to disable the check or this warning:
See https://handlebarsjs.com/api-reference/runtime-options.html#options-to-control-prototype-access for details
Handlebars: Access has been denied to resolve the property "branches" because it is not an "own property" of its parent.
You can add a runtime option to disable the check or this warning:
See https://handlebarsjs.com/api-reference/runtime-options.html#options-to-control-prototype-access for details
Handlebars: Access has been denied to resolve the property "functions" because it is not an "own property" of its parent.
You can add a runtime option to disable the check or this warning:
See https://handlebarsjs.com/api-reference/runtime-options.html#options-to-control-prototype-access for details
Handlebars: Access has been denied to resolve the property "lines" because it is not an "own property" of its parent.
You can add a runtime option to disable the check or this warning:
See https://handlebarsjs.com/api-reference/runtime-options.html#options-to-control-prototype-access for details
Test Suites: 1 failed, 1 total
Tests: 0 total
Snapshots: 0 total
Time: 0.827s
Ran all test suites.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Exited with code exit status 1Note: When I run npm test --openssl-legacy-provider on my local machine (Windows 10), I get the exact same error
Some Questions
- Why are we using yarn for testing/development when
Buefy/Buefyis usingNPM? - Why are the test now failing?
kikuomax
codecov-commenter
The Problem: The NPM publish workflow failed to run because no
package-lock.jsonwas present in the root directory. This should have been easily generated by runningnpm install. However, there were some dependency issues involvingeslintand some in house dependencies used for configuringeslintin thenuxt-buefyproject.The Presented Solution (in this PR):
eslint-config-buefyto the latest version (v0.0.3)eslintin thenuxt-buefyproject tov4.18.2to solve the conflict to allownpm installto generate thepackage-lock.jsonfilepackage-lock.jsonin the event it is not pushed to GitHub.