I'm using NeXTs and sanity for this project; Yesterday This code was worked but I delete the node modules folder for sending the project to a friend
But today when I reinstall the Node module folder it shows me this error and I can't find why it doesn't work!!
The error look like this
This the code for get data from sanity
And This is the code for fetching data
i try to reinstall node module packages for many time i'ma using --legacy-peer-deps but the error Doesn't disappear
Related
I have an issue and it wont let me create a component because of mismatch versions, I tried deleting vue-loader, vue-template-compiler node modules. Deleting #vue/compiler-sf an reinstalling etc and i always get the same message.
new components
(use "bit tag --all [version]" to lock a version with all your changes)
> test-test ... issues found
error found while parsing the file (edit the file and fix the parsing error):
src/components/testTest.vue ->
Vue packages version mismatch:
vue#3.2.31 (C:\Users\Alex 2019\AppData\Roaming\npm\node_modules\vue\index.js)
vue-template-compiler#2.7.13 (C:\Users\Alex 2019\AppData\Roaming\npm\node_modules\bit-bin\node_modules\vue-template-compiler\package.json)
This may cause things to work incorrectly. Make sure to use the same version for both.
If you are using vue-loader#>=10.0, simply update vue-template-compiler.
If you are using vue-loader#<10.0 or vueify, re-installing vue-loader/vueify should bump vue-template-compiler to the latest.
I am trying to simply upgrade the version of vue3 we are running at work from v3.2.31 to v3.2.40. However, when I do, I am now getting an error in the runtime-dom.d.ts
Below is a screen shot from the file with vue v3.2.31 installed.
Once I've run the "npm update vue --save" command, the file looks like this (v3.2.40)...
...and VS 2022 throws the following error when trying to build...
If I delete the line from my local copy of runtime-dom.d.ts, all works as before. My problem comes when deploying the solution to the development environment etc. The npm install step puts a version of the runtime-dom.d.ts that does still have this line.
I'd like to fix this without having to resort to hacking the runtime-dom.d.ts file if at all possible.
Many thanks in advance.
Details
I am getting a build failure of my read-the-docs that I don't understand. The assertion of "verbatim" in line 2151 of nbsphinx.py is causing the build failure. So the build fails when I try to include the Jupyter Notebook tutorials I created. I compared current versions of the tutorials to previous versions which had not caused the build to fail, and I can't find a difference that could account for the current failure.
Read the Docs project URL: lofti_gaia
Build URL: https://github.com/logan-pearce/lofti_gaia
Read the Docs username: logan-pearce
Expected Result
A passing build including *.ipynb files
Actual Result
Build failed at line 2151 of nbsphinx.py due to assertion of 'Verbatim' failing.
Terminal output:
Running Sphinx v4.1.2
loading translations [en]... done
making output directory... done
WARNING: html_static_path entry '_static' does not exist
loading pickled environment... done
building [mo]: targets for 0 po files that are out of date
building [latex]: all documents
updating environment: 0 added, 0 changed, 0 removed
looking for now-outdated files... none found
processing lofti_gaia.tex... index installation tutorials/QuickStart tutorials/Tutorial api lofti loftitools
resolving references...
done
writing... failed
Exception occurred:
File "/home/docs/checkouts/readthedocs.org/user_builds/lofti-gaia/conda/latest/lib/python3.7/site-packages/nbsphinx.py", line 2151, in depart_codearea_latex
assert 'Verbatim' in lines[0]
AssertionError
The full traceback has been saved in /tmp/sphinx-err-x1h83s3m.log, if you want to report the issue to the developers.
Please also report this if it was a user error, so that a better error message can be provided next time.
A bug report can be filed in the tracker at <https://github.com/sphinx-doc/sphinx/issues>. Thanks!
According to the github issue 584 for nbsphinx (https://github.com/spatialaudio/nbsphinx/issues/584), this is due to a compatibility issue with sphinx 4.1.0. It can be gotten around by requiring sphinx version 4.0.2.
So in my requirements.txt file, I included sphinx==4.0.2, after which the build passes. So now my requirements.txt file looks like:
numpy
matplotlib
astropy>=4.0.1.post1
astroquery>=0.4
sphinx==4.0.2
ipython==7.19.0
nbsphinx>=0.8.6
and the build passes.
I have encountered the same issue. I did not solve it with .ipynb format, but converting the jupyter notebook to .rst format works.
May it helps
I have installed the new BigQuery export firebase extension on my firestore database and it works great.
Now I am trying to import the existing data in the collection by following the instructions on the extension but getting the error below.
https://github.com/firebase/extensions/blob/master/firestore-bigquery-export/guides/IMPORT_EXISTING_DOCUMENTS.md
Any ideas how to resolve this error?
Note: I ran gcloud components update to update to the latest gcloud versions
npx #firebaseextensions/fs-bq-import-collection
Importing data from Cloud Firestore Collection: members, to BigQuery Dataset: qmtbc_dev_export, Table: members_raw_changelog
Error unlinking journal file C:\Users\fullo\AppData\Roaming\npm-cache\_npx\10884\node_modules\#firebaseextensions\fs-bq-import-collection\lib/from-members-to-qmtbc-dev:qmtbc_dev_export:members_raw_changelog
after successful import: Error: ENOENT: no such file or directory, unlink 'C:\Users\fullo\AppData\Roaming\npm-cache\_npx\10884\node_modules\#firebaseextensions\fs-bq-import-collection\lib\from-members-to-qmtbc-dev:qmtbc_dev_export:members_raw_changelog'
---------------------------------------------------------
Finished importing 0 Firestore rows to BigQuery
---------------------------------------------------------
Error importing Collection to BigQuery: Error: EPERM: operation not permitted, unlink 'C:\Users\fullo\AppData\Roaming\npm-cache\_npx\10884\node_modules\#firebaseextensions\fs-bq-import-collection\node_modules\grpc\src\node\extension_binary\node-v64-win32-x64-unknown\grpc_node.node'
Update 1:
I have been stuck on this for over 24hrs now.
I have reinstalled nodejs to v12.13 and killed my virus checker, rebooted etc
No luck.
Also tried npm rebuild
The closest issues I have seen are:
https://github.com/phoenixframework/phoenix/issues/2464#issuecomment-325497850
https://github.com/phoenixframework/phoenix/issues/2464#issuecomment-328853460
Update 2:
I have uninstalled node and tried versions 8.16.2, 10.17 and 12.13
I deleted my npm and npm cache folders and reinstalled my global node packages.
Still no luck. I may try this method instead: https://cloud.google.com/bigquery/docs/loading-data-cloud-firestore
Update 3:
I have given up. It would be good to know if this script actually works for others.
It does work. You just need to go to the IAM page in the Google Cloud Platform dashboard and give the user enough rights. Add a role with enough permissions to create a BigQuery datasets.
you have to export GOOGLE_APPLICATION_CREDENTIALS json file first and then issue npx #firebaseextensions/fs-bq-import-collection command
I installed some new plugin on Paw app (Postman 1 and 2 export, Swagger 2). And since I have this error when I try to make a new export. I tried to uninstall and reinstall only one plugin, and I still have this error.
But before I install some new plugin, I made some export without error.
This is the error I get when I attempt to make an export:
Export Failed
JavaScript Exception: TypeError: undefined is not an object (evaluating 'ds.length') ({
column = 20;
line = 2277;
})
Sorry for the very late follow up. We've been able to reproduce this issue, and release a fix last week.
Please update your Paw extensions by going to the Paw menu > Extensions > Check for Extensions Updates…
This will trigger the updating of all your installed extensions. Then, please try again to export your project, it should be working correctly.