I was migrating to sveltekit 1.7.2 from 1.5.3, as there was a security vulnerability. NPM did not tell me that 1.7.2 was a breaking change, so I installed the new version. I found that the latest compatible version was 1.5.6, anything higher resulted in the same error. I don't know why this is an issue, I guess it wouldn't be if you were making a new project, but as I am not doing that, can anyone tell me how to fix this?
Entire error:
Error: Cannot find module '__sveltekit/paths' imported from [path to project]/node_modules/#sveltejs/kit/src/runtime/server/respond.js'
at nodeImport (file:///[path to project]/vite/dist/node/chunks/dep-3007b26d.js:52431:25)
at ssrImport (file:///[path to project]/node_modules/vite/dist/node/chunks/dep-3007b26d.js:52354:20)
at eval (/node_modules/#sveltejs/kit/src/runtime/server/respond.js:5:37)
at async instantiateModule (file://path to project]/node_modules/vite/dist/node/chunks/dep-3007b26d.js:52400:9)
This error tells me that the file "__sveltekit/paths" has either moved, been replaced, or deleted entirely. Does anyone know where the file is now/if it even still exists?
Please note, that I see this error in the browser and in the node console. No other content is rendered at all.
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've been trying to setup firebase in my app for a while now with no luck.
Immediately I install the lastest version of com.google.firebase:firebase-auth -> 21.0.6 which is required for setting up firebase, I get the above error which doesn't seem to go away no matter what unless I remove the package.
I looked around everywhere to see if it's defined somewhere in the package to change it but it's no where to be found.
Finally tracked it down in the dependencies tree, it only appears once and it seems to be resolving to 9.8.0 in the following line
com.google.android.gms:play-services-auth-api-phone:17.4.0 -> 9.8.0 FAILED
Things i've tried (Basically anything I could find on it or anything similar on the internet)
Installed different version of the firebase dependencies auth & app (even to versions where play-services-auth-api-phone had not been introduced as a dependency and it still does not work.
Moved around a couple things in my /build.gradle, jcenter, google(), etc to no luck
Played around with different versions of play-services and gradle.
Any help will be much appreciated.
Also this is the error that gets thrown when running the project:
> Could not resolve all files for configuration ':app:debugRuntimeClasspath'.
Could not find com.google.android.gms:play-services-auth-api-phone:9.8.0.
Searched in the following locations:
- file:/C:/Users/username/.m2/repository/com/google/android/gms/play-services-auth-api-phone/9.8.0/play-services-auth-api-phone-9.8.0.pom
- file:/D:/Github/app_name/node_modules/react-native/android/com/google/android/gms/play-services-auth-api-phone/9.8.0/play-services-auth-api-phone-9.8.0.pom
- file:/D:/Github/app_name/node_modules/jsc-android/dist/com/google/android/gms/play-services-auth-api-phone/9.8.0/play-services-auth-api-phone-9.8.0.pom
- https://maven.google.com/com/google/android/gms/play-services-auth-api-phone/9.8.0/play-services-auth-api-phone-9.8.0.pom
- https://dl.google.com/dl/android/maven2/com/google/android/gms/play-services-auth-api-phone/9.8.0/play-services-auth-api-phone-9.8.0.pom
- https://www.jitpack.io/com/google/android/gms/play-services-auth-api-phone/9.8.0/play-services-auth-api-phone-9.8.0.pom
- https://jcenter.bintray.com/com/google/android/gms/play-services-auth-api-phone/9.8.0/play-services-auth-api-phone-9.8.0.pom
Required by:
project :app > project :react-native-firebase_auth > com.google.firebase:firebase-auth:21.0.6
I'm trying to run my first deno script which is pretty much from the denoDB docs, it just tries to connect to a database with a SQLite3 connector (I'm on a Macbook pro so it should be installed):
import { Database, SQLite3Connector } from 'https://deno.land/x/denodb/mod.ts';
const connector = new SQLite3Connector({
filepath: './db.sqlite',
});
export const db = new Database(connector);
I'm running deno run api/db.ts and I get this error after a few successful downloads:
Download https://deno.land/std#0.149.0/encoding/hex.ts
Download https://deno.land/std#0.149.0/hash/_wasm/lib/deno_hash.generated.mjs
error: Import 'https://dev.jspm.io/inherits#2.0' failed: 500 Internal Server Error
at https://raw.githubusercontent.com/Zhomart/dex/930253915093e1e08d48ec0409b4aee800d8bd0c/lib-dyn/deps.ts:4:26
I've deleted my /Users/<me>/Library/Caches/deno/deps/https and reran the script a few times but I still can't get past this. In my browser trying to follow the URL https://dev.jspm.io/inherits#2.0 does give me an error. What is going on here? There's not much code and I imagine it's not broken for everybody. What do I need to do to get this script to run without issues?
EDIT: it seems to be a library error https://github.com/eveningkid/denodb/issues/348
This is an error caused by a nested depedency, from a project that is not maintained.
See this for more info: [https://jspm.org/jspm-dev-release]
The point is dev.jspm.io is now jspm.dev
A way to fix this is to fork and update depedencies.
Another thing, if you're not using deno deploy, you can just use this as a replacement for your denodb: https://raw.githubusercontent.com/joeldesante/denodb/master/mod.ts
Just note that this script is no more maintained either, but it will fix your problem
Edit
I just made a dirty quick fix for deno deploy use this as a depedency isntead of denodb: https://raw.githubusercontent.com/ninjinskii/denodb/master/mod.ts
Again, i may not maintain this script forever.
The best thing that can happen is an update from these libs maintainers
I am using Angular2-Meteor, TypeScript. (Meteor version 1.3.2.4)
When I use console.log('test'); on the server side, it is working well.
However, I got this warning in my terminal:
Cannot find name 'console'.
How can I get rid of this warning?
Or is there any special method such as Meteor.log for server side? Thanks
How can I get rid of this warning?
if its a TypeScript compiler warning (and not a runtime one) then console is defined in lib.d.ts : https://basarat.gitbooks.io/typescript/content/docs/types/lib.d.ts.html
Make sure that the compiler is setup correctly (e.g. doesn't have --noLib or some custom incorrect --lib). You might want to look at your tsconfig.json's compilerOptions (if any)
#barbatus who is main contributor for angular2-meteor, gave the answer on Github.
The issue is in that TypeScript package uses lib.core.ts default lib on the server side which doesn't have definitions for console. NodeJS definitions from other side as now defines console in the global scope only (i.e. global.console).
The solution is running this in your terminal:
typings install registry:env/meteor --ambient
Please go here for more details.
I usually use trigger.io to generate my ipa-Files for iOS. Now when I want to generate the file, I get the following error message:
Failed when running /usr/bin/codesign: codesign_allocate: object: /Users/mherceg/Desktop/ag-app/development/ios/device-ios.app/Forge malformed object (unknown load command 39)
/Users/mherceg/Desktop/ag-app/development/ios/device-ios.app: object file format unrecognized, invalid, or unsuitable
It worked yesterday, but now it doesn't. Any help is very welcome.
Thanks,
enne
This is probably to do with v1.4.16 of our platform, where we switched over to building on Xcode 4.5: I'd recommend upgrading Xcode and make sure the Command-line Tools (Preferences ↦ Downloads) are installed.