-
Notifications
You must be signed in to change notification settings - Fork 32
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
Add more modules #6
Comments
hey mastilver - seems you arent maintaining this anymore - just wondering what your thoughts are? is it not useful enough? |
Hi @sw-yx 👋 I saw your slides, really cool 👍 |
hey thanks for the reply!! I was just thinking, maybe theres a way to define a default rule for module-to-cdn to map for any arbitrary library. I don't really like this whitelisting approach because it doesn't scale. since you can define modules to exclude/include in as a further extra step, we could build in some sort of "ping" to validate the module-to-cdn result during the web pack build process. it would slow down the build but then guarantee that this autogenerated module-to-cdn mapping is valid for a particular library and version. what do you think? |
I wish that was possible... but not everybody is using the same pattern
Can you explain that, I didn't get it... |
We could use https://packd.now.sh/ but I'm not sure if it's out of beta yet |
not sure. im not going to work on this right now as I don't have much better ideas. but I think its a really good idea that I will probably come back to in future. |
The text was updated successfully, but these errors were encountered: