-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Want to learn: "@sveltejs/kit": "npm:@tal500/[email protected]", where did this package pull from? Do you have an article? #3
Comments
I used Google translate and the result is "thanks thanks". You're welcome! |
Want to learn: "@sveltejs/kit": "npm:@tal500/[email protected]", where did this package pull from? Do you have an article? |
The main content is the title, not just the content. Hey hey |
Ah OK, please write this in English so I can understand better. You asked where the package is from, so the short answer is: This is a fork of SvelteKit 'kit' package I'm maintaining of PR sveltejs/kit#6265(and all the info appears there), until hopefully legacy support will be merged. Hope it answers, you're welcome also to maintain your own fork of PR sveltejs/kit#6265 if you wish to use it carefully since it's unofficial. Additionally, I'll edit and translate your messages for now. |
Oh, oh, OK. Thank you for your answer. Originally, it was also published to the npm repository. I am just wondering why we need to specify an npm:? |
This line of code: sveltekit-legacy-demo/package.json Line 18 in 565de06
tells to NPM: "Install the package @tal500/[email protected], but name it as a package named "@sveltejs/kit"". This makes all the sveltekit-legacy-demo/vite.config.js Line 3 in 565de06
|
Oh, I see. Thanks for clarification |
Thanks thank you
The text was updated successfully, but these errors were encountered: