Giters

PlayForm / Compress

🗜️ Compress —

Home Page:https://NPMJS.Org/@playform/compress

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

astro-compress is gone from NPM registry

saif71 opened this issue · comments

commented

Like the title suggest. It is gone from the NPM registry.
https://www.npmjs.com/package/astro-compress

image

commented

The author closed their NPM account; they'll make a new one shortly #162

commented

How long will it take? My website is down now... because my pipeline can't do a rebuild.

commented

same problem here.

commented

same problem for me as well :(

commented

Guess this is the life with open source. I suggest you :

  1. temporarily remove the package from your project (I did it this evening.)
  2. Use another similar package for now.
commented

same here

commented

@NikolaRHristov can you take a look at this please?

commented

Ok, I have regained access to the astro-compress, astro-critters, astro-rome and files-pipe packages. These will be republished.

commented

After I have republished, I will transfer the packages to @FredKSchott, if that's okay.

commented

@NikolaRHristov Why is version 2.0.0 empty in NPM? Could you please fix it?

commented

Build seems to fail when using v2.0.0.

error   Failed to resolve entry for package "astro-compress". The package may have incorrect main/module/exports specified in its package.json.
commented

I'm receiving the same error as @jmblog

commented

Can you please publish release 1.1.50 on NPM?

commented

Hello, @zoxon, version 2.0 is empty as to not get malwared. @jmblog, @benstegink just use @otterlord/astro-compress in the meantime while this gets fixed. @Igloczek, no, because it uses files-pipe which is currently missing.

These will all be resolved by the end of the day. NPM does not allow republishing of packages over 24 hours so I'll have to wait. Their support haven't answered me still.

This is why I'm republishing empty packages so as to them not getting malwared. Everything will be fixed. I have the source code offline.

commented

+1

commented

The author closed their NPM account; they'll make a new one shortly #162

why?

commented

@aetherclouds Bro wok up in the morning and choose violence. 😂

commented

@aetherclouds Bro wok up in the morning and choose violence. 😂

just genuinely curious, sorry if it came off the wrong way!

commented

@aetherclouds Bro wok up in the morning and choose violence. 😂

just genuinely curious, sorry if it came off the wrong way!

Hi, I'm exiting Open-Source, if that's a thing, and just did it the wrong way. I thought it would archive the packages leaving everything intact. Now two more days days of pressure 😅.

Progress so far:

I should get astro-compress, astro-critters and astro-rome up in a few hours, as well. Just testing a few more things and making sure everything is working correctly.

commented

@aetherclouds Bro wok up in the morning and choose violence. 😂

just genuinely curious, sorry if it came off the wrong way!

Hi, I'm exiting Open-Source, if that's a thing, and just did it the wrong way. I thought it would archive the packages leaving everything intact. Now two more days days of pressure 😅.

Progress so far:

I should get astro-compress, astro-critters and astro-rome up in a few hours, as well. Just testing a few more things and making sure everything is working correctly.

don't down on yourself I'm sure nobody would predict something like that happening right upon deleting their account :)
good luck on your new ventures and thanks for the neat libraries!

commented

😅 Thank you! @aetherclouds

commented

@NikolaRHristov so if I understand it correctly, you removed your NPM account before transfer that packages to @FredKSchott but what about this you said "Hello, @zoxon, version 2.0 is empty as to not get malwared". Before the packages had malware?

commented

@NikolaRHristov so if I understand it correctly, you removed your NPM account before transfer that packages to @FredKSchott but what about this you said "Hello, @zoxon, version 2.0 is empty as to not get malwared". Before the packages had malware?

No, 24 hours after my account was deleted these packages were free for anyone to claim.

commented

I setup a script to automatically re-publish those packages every 5 minutes. These packages were empty because some things were not working correctly and I didn't want to publish broken packages, so just empty ones seemed like a better alternative.

You can still see the source online https://github.com/astro-community/astro-compress. There is no malware there.

Also, I publish all of my packages with Provenance, which means that they are verified by a commit and published from GitHub. You can still see the little box at the bottom https://www.npmjs.com/package/files-pipe
image

This is how astro-compress, astro-critters and astro-rome were and will also be published in the future, as well.

commented

I setup a script to automatically re-publish those packages. The packages were empty because some things were not working correctly and I didn't want to publish broken packages, so just empty ones seemed a better alternative.

You can still see the source online. There is no malware there.

Also, I publish all of my packages with Provenance, which means that they are verified by a commit and published from GitHub. You can still see the little box at the bottom https://www.npmjs.com/package/files-pipe image

This is how astro-compress, astro-critters and astro-rome were and will also be published in the future, as well.

Okay I understand, you republished the package to prevent some get the package name and distribute malware. And not that your package had malware.

commented

Okay I understand, you republished the package to prevent some get the package name and distribute malware. And not that your package had malware.

Yes, correct, as a preemptive measure.

commented

@aetherclouds Bro wok up in the morning and choose violence. 😂

just genuinely curious, sorry if it came off the wrong way!

Hi, I'm exiting Open-Source, if that's a thing, and just did it the wrong way. I thought it would archive the packages leaving everything intact. Now two more days days of pressure 😅.

Progress so far:

I should get astro-compress, astro-critters and astro-rome up in a few hours, as well. Just testing a few more things and making sure everything is working correctly.

you deserve an award, honestly

commented

@aetherclouds Bro wok up in the morning and choose violence. 😂

just genuinely curious, sorry if it came off the wrong way!

Hi, I'm exiting Open-Source, if that's a thing, and just did it the wrong way. I thought it would archive the packages leaving everything intact. Now two more days days of pressure 😅.
Progress so far:

I should get astro-compress, astro-critters and astro-rome up in a few hours, as well. Just testing a few more things and making sure everything is working correctly.

you deserve an award, honestly

That would be @TheOtterlord, he pulled up and created a backup, archive and published everything almost instantly.

https://www.npmjs.com/package/@otterlord/astro-compress
https://www.npmjs.com/package/@otterlord/astro-critters
https://www.npmjs.com/package/@otterlord/astro-rome

commented

Thanks for the healthy reminder to always check the issues page haha

commented

astro-compress v2.0.1 has been restored with Provenance

This repository https://github.com/baxast/astro-compress will soon be synchronized with the official astro-community one https://github.com/astro-community/astro-compress.

You can submit issues in either.

astro-critters and astro-rome coming up next.

commented

Thanks for the hustle! Well done 👍

commented

astro-critters up too - PlayForm/Inline#137 v2.0.2

commented

I tried v2.0.2, but the exclude option appears to be ignored. I recall that it worked in the previous version.

import compress from "astro-compress";

export default {
    integrations: [
        compress({
            exclude: [
                'dist/images/articles/*',
                'dist/images/banners/*',
                'dist/images/experts/*',
                'dist/images/top_banners/*',
            ],
        }),
    ],
};
commented

I tried v2.0.2, but the exclude option appears to be ignored. I recall that it worked in the previous version.

import compress from "astro-compress";

export default {
    integrations: [
        compress({
            exclude: [
                'dist/images/articles/*',
                'dist/images/banners/*',
                'dist/images/experts/*',
                'dist/images/top_banners/*',
            ],
        }),
    ],
};

Try Exclude

commented

@NikolaRHristov hey, I add astro-compress v2.0.2 to my app and got such errors:

  • The package "stream" wasn't found on the file system but is built into node.
  • The package "stream" wasn't found on the file system but is built into node.
  • 'etc...' into node.

If I remove astro-compress v2.0.2 and add @otterlord/astro-compress everything is fine in local but the issue is nothing appears on the app (white blank page after Cloudflare deployment)

commented
  • stream

Hi, does this happen with the latest version v2.0.5?

commented

Hi, does this happen with the latest version v2.0.5?

I update it to the latest version and yes the issue still there

commented

Hi, does this happen with the latest version v2.0.5?

I update it to the latest version and yes the issue still there

commented

Could you please share your tsconfig.json or some more information like build logs, etc. so we can debug this further. You can message me privately on Discord at nikolahristov