Open TempAccountNull opened 1 year ago
Techassi
commented
1 year ago Yeah I have removed this package from the NPM registry as well as my personal GitHub since the package wasn't used quite as often...
However, I can re-create the repo and re-publish the package on NPM if needed.
TempAccountNull
commented
1 year ago Yeah I have removed this package from the NPM registry as well as my personal GitHub since the package wasn't used quite as often...
However, I can re-create the repo and re-publish the package on NPM if needed.
Please do if you can. I attempted to email you about this.
Techassi
commented
1 year ago Oh yeah you did - my bad, didn't see it. I will re-publish as fast as possible.
Techassi
commented
1 year ago I published the code to my repository. I will publish version 1.0.0 again with the current code base. Release 1.0.1 will include a new toolchain based on PNPM and Vite.
Techassi
commented
1 year ago I now published the package under version 1.0.1. Publishing under 1.0.0 was not possible due to an error. NPM complained about that it "cannot publish over previously published version '1.0.0'". This seems a little weird as the package no longer exists, but oh well...
You can now use the package with version 1.0.1. Version 1.0.2 will switch to a new toolchain.
TempAccountNull
commented
1 year ago I now published the package under version 1.0.1. Publishing under 1.0.0 was not possible due to an error. NPM complained about that it "cannot publish over previously published version '1.0.0'". This seems a little weird as the package no longer exists, but oh well...
You can now use the package with version 1.0.1. Version 1.0.2 will switch to a new toolchain.
I really appreciate your time man. It helps a whole lot as this project really needs some TLC since most of these modules are super out of date or vulnerable.
[X] Still marked as unable to build via source.
An update on the build process until @sgtaziz can update his repo with fixing this for clones.
Warning:
The file: package.json will require a manual edit to fix this package since the 1.0.0 doesn't exist anymore and node 14 is depreciated.
To fix this for newer node revisions find the following:
"main": "background.js",
"dependencies": {
"@fortawesome/fontawesome-svg-core": "^1.2.34",
"@fortawesome/free-solid-svg-icons": "^5.15.2",
"@fortawesome/vue-fontawesome": "^3.0.0-3",
"@techassi/vue-lazy-image": "^1.0.0",Then save the file, yarn will not complain about it. However, node-sass has been depreciated and I tried changing it out for the following with another issue for vue-lazy-image,
Change
"node-sass": "^4.12.0",with
"sass": "^1.58.3", ERROR Failed to compile with 1 error 2:58:03 AM
error in ./node_modules/@techassi/vue-lazy-image/lib/vue-lazy-image.esm.js
Module parse failed: Unexpected token (48:26)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
| return;
| }
> this.observer?.unobserve(target);
| this.callbacks[id]();
| });
@ ./src/main.ts 22:0-52 34:8-20
@ multi (webpack)-dev-server/client?http://192.168.0.21:8080&sockPath=/sockjs-node (webpack)/hot/dev-server.js ./src/main.ts
No issues found.Get the following error
ERROR Failed to compile with 1 error 3:55:24 AM
error in ./src/views/Home/index.vue?vue&type=style&index=0&id=1d9b105c&lang=scssSyntax Error: TypeError: this.getOptions is not a function
@ ./node_modules/vue-style-loader??ref--8-oneOf-1-0!./node_modules/css-loader/dist/cjs.js??ref--8-oneOf-1-1!./node_modules/vue-loader-v16/dist/stylePostLoader.js!./node_modules/postcss-loader/src??ref--8-oneOf-1-2!./node_modules/sass-loader/dist/cjs.js??ref--8-oneOf-1-3!./node_modules/cache-loader/dist/cjs.js??ref--0-0!./node_modules/vue-loader-v16/dist??ref--0-1!./src/views/Home/index.vue?vue&type=style&index=0&id=1d9b105c&lang=scss 4:14-457 15:3-20:5 16:22-465 @ ./src/views/Home/index.vue?vue&type=style&index=0&id=1d9b105c&lang=scss @ ./src/views/Home/index.vue @ ./node_modules/cache-loader/dist/cjs.js??ref--12-0!./node_modules/babel-loader/lib!./node_modules/cache-loader/dist/cjs.js??ref--0-0!./node_modules/vue-loader-v16/dist??ref--0-1!./src/App.vue?vue&type=script&lang=js @ ./src/App.vue?vue&type=script&lang=js @ ./src/App.vue @ ./src/main.ts @ multi (webpack)-dev-server/client?http://192.168.0.21:8080&sockPath=/sockjs-node (webpack)/hot/dev-server.js ./src/main.ts
No issues found.
sgtaziz
commented
1 year ago Unfortunately I haven't been able to update WebMessage since I no longer have a jailbreakable device. But, I will try to update the dependencies to fix the build later today!
sgtaziz
commented
1 year ago @Techassi seems like version 1.0.1 is different than the previous 1.0.0. It is throwing some errors as stated above.
I've uploaded the old one to my repo here https://github.com/sgtaziz/WebMessage/tree/main/src/components/%40techassi/vue-lazy-image to get around this for now. If it is an issue, please let me know and I will remove it ASAP!
sgtaziz
commented
1 year ago @TempAccountNull Ok, the latest commits should have fixed the issue. It is building on my local system and TravisCI, let me know if you need anymore help!
Techassi
commented
1 year ago I really appreciate your time man. It helps a whole lot as this project really needs some TLC since most of these modules are super out of date or vulnerable.
Sure thing. Love to help out! The next version will include some improvements and a new toolchain as I already mentioned. I aim to release the next version around the end of march.
@TempAccountNull Ok, the latest commits should have fixed the issue. It is building on my local system and TravisCI, let me know if you need anymore help!
So is it building with the NPM version (v1.0.1)? I haven't changed any of the code since I initially removed the package and repo. If there are any issues, I will look into them.
I've uploaded the old one to my repo here https://github.com/sgtaziz/WebMessage/tree/main/src/components/%40techassi/vue-lazy-image to get around this for now. If it is an issue, please let me know and I will remove it ASAP!
This should be fine... The best solution is of course to fix the build issues and have the fixes on NPM. But for now, let's use the local version.
sgtaziz
commented
1 year ago Agreed. Just wanted to have something working for people to clone off of.
But the version I have on my repo (which is an old local build I found in my node_modules) is different than the one you have uploaded. It could be that it was just not updated, but it does show version 1.0.0
Module parse failed: Unexpected token (48:26)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
| return;
| }
> this.observer?.unobserve(target);
| this.callbacks[id]();
| });The line highlighted in this error, which is what I was receiving using the 1.0.1 version, is not in the codebase on the old one. The NPM version seems different from what was there before @Techassi
TempAccountNull
commented
1 year ago @Techassi @sgtaziz Got another contact like discord I can immediately message a response on?
So is it building with the NPM version (v1.0.1)? I haven't changed any of the code since I initially removed the package and repo. If there are any issues, I will look into them.
I've uploaded the old one to my repo here https://github.com/sgtaziz/WebMessage/tree/main/src/components/%40techassi/vue-lazy-image to get around this for now. If it is an issue, please let me know and I will remove it ASAP!
This should be fine... The best solution is of course to fix the build issues and have the fixes on NPM. But for now, let's use the local version.
This does not build on node 15+ only node 14 due to the dependencies being out of date as stated above which this is using .Node 14 | 4.14 npm info using npm@9.5.1 npm info using node@v16.14.2
Node 16 | or package dependacy 6.0+ is a requirement as stated above.
Phone Info (irrelevance)
iOS version: 14.2 Jailbreak: Unc0ver Tweak Version: Latest (0.62)
BUILD INFO
Issue: Upon cloning and trying to build this source with yarn install the user building will experience multiple errors with vue.
Package.json (where the issue relies)
ERROR LOG IN QUESTION
yarn install v1.22.19 [1/4] Resolving packages... [2/4] Fetching packages... error An unexpected error occurred: "https://registry.yarnpkg.com/@techassi/vue-lazy-image/-/vue-lazy-image-1.0.0.tgz: Request failed \"404 Not Found\"". info If you think this is a bug, please open a bug report with the information provided in "scripts\vue-lazy-image\2\WebMessage-main\WebMessage-main\yarn-error.log". info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.