#semvar — Public Fediverse posts

The motivation for #semvar seems to be eliminating duplicated modules in your bundle, but it seems to me that with HTTP modules, the browser cache should handle duplicated modules just fine.

Bundling is an anti-pattern now that we have #ESM in the browser!

#webDev

The motivation for #semvar seems to be eliminating duplicated modules in your bundle, but it seems to me that with HTTP modules, the browser cache should handle duplicated modules just fine.

Bundling is an anti-pattern now that we have #ESM in the browser!

#webDev

The motivation for #semvar seems to be eliminating duplicated modules in your bundle, but it seems to me that with HTTP modules, the browser cache should handle duplicated modules just fine.

Bundling is an anti-pattern now that we have #ESM in the browser!

#webDev

The motivation for #semvar seems to be eliminating duplicated modules in your bundle, but it seems to me that with HTTP modules, the browser cache should handle duplicated modules just fine.

Bundling is an anti-pattern now that we have #ESM in the browser!

#webDev

The motivation for #semvar seems to be eliminating duplicated modules in your bundle, but it seems to me that with HTTP modules, the browser cache should handle duplicated modules just fine.

Bundling is an anti-pattern now that we have #ESM in the browser!

#webDev

I don't want to publish to #NPM because that organization has been shitty for a decade now.

#JSR seems like more of the same.

Why didn't #HTTP based #ESM #packageManagement catch on? #JSR says it's because you can't do #semvar, but I don't see why not; just use file paths ("example.com/package/major/minor/patch/")

I don't see an advantage to publishing #modules to a #package #registry at this time.

#webDev #javaScript #web #programming

I don't want to publish to #NPM because that organization has been shitty for a decade now.

#JSR seems like more of the same.

Why didn't #HTTP based #ESM #packageManagement catch on? #JSR says it's because you can't do #semvar, but I don't see why not; just use file paths ("example.com/package/major/minor/patch/")

I don't see an advantage to publishing #modules to a #package #registry at this time.

#webDev #javaScript #web #programming

I don't want to publish to #NPM because that organization has been shitty for a decade now.

#JSR seems like more of the same.

Why didn't #HTTP based #ESM #packageManagement catch on? #JSR says it's because you can't do #semvar, but I don't see why not; just use file paths ("example.com/package/major/minor/patch/")

I don't see an advantage to publishing #modules to a #package #registry at this time.

#webDev #javaScript #web #programming

I don't want to publish to #NPM because that organization has been shitty for a decade now.

#JSR seems like more of the same.

Why didn't #HTTP based #ESM #packageManagement catch on? #JSR says it's because you can't do #semvar, but I don't see why not; just use file paths ("example.com/package/major/minor/patch/")

I don't see an advantage to publishing #modules to a #package #registry at this time.

#webDev #javaScript #web #programming

I don't want to publish to #NPM because that organization has been shitty for a decade now.

#JSR seems like more of the same.

Why didn't #HTTP based #ESM #packageManagement catch on? #JSR says it's because you can't do #semvar, but I don't see why not; just use file paths ("example.com/package/major/minor/patch/")

I don't see an advantage to publishing #modules to a #package #registry at this time.

#webDev #javaScript #web #programming