Skip to content
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

[Feature]: Strong Support for Standards #2341

Open
christopherreay opened this issue Jan 26, 2025 · 1 comment
Open

[Feature]: Strong Support for Standards #2341

christopherreay opened this issue Jan 26, 2025 · 1 comment
Assignees
Labels
feature New feature or request

Comments

@christopherreay
Copy link

Is your request related to a problem?

So this code base is clearly much more... grounded and professional that appKit / rainbow. I can see that a mile off.

I want to ask a favour, I think it is important... Please can you support the CDN standards in your documentation. Webpack / Vite are not a standards tooling, they are a gateway blocker for standards in general. The issue of efficiently including libraries has already been solved, and the whole world where people "need" to import them into node.js and have a tool "pack them" into a browser format is part of the assault on standards by corporations, and people on the bandwagon.

Would really appreciate a CDN setup in the docs. its very important to me.

ive just been build on react / crypto space, and its clear the web is being saturated to make stuff that pulls young devs away from standards as if the standards are broken, or do not exist, and as if the anti-patterns of tailwind and... SSR and all this stuff are the only reality. Its ... frightening to me to be frank. tyty

Feature Description

No response

Alternative Solutions

No response

Anything else?

No response

@christopherreay christopherreay added the feature New feature or request label Jan 26, 2025
@christopherreay
Copy link
Author

So I ve just been reading this: https://onboard.blocknative.com/docs/modules/core#build-environments

it seems like... there is a clear commitment to make sure that people can build without blocking or opinionated dependencies ,which is great... maybe I am missing something.

Is there some technical, or otherwise.... philosophical reason that a functioning build is not available on CDN? or is there one available on CDN somewhere?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants