-
Notifications
You must be signed in to change notification settings - Fork 112
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
Have this package available on CDNJS #30
Comments
Tagging @DamianEdwards @jbagga FYI |
@jbagga, did we decide not to do this? |
Yes the decision was to have this package on NuGet and Microsoft Ajax CDN only cc @Eilon |
That's right, closing. |
Library Manager currently only uses CDNJS and file system. |
Please reopen this issue and add the AJAX unobtrusive to CDNJS. Generally, Microsoft developer tools and products should match up and offer some semblance of continuity. Thanks, |
@mkArtakMSFT please have a look. |
Can you please do this soon as currently I have no means of using a VS client package manager (be it LibMan or NPM) to get a local copy without manually downloading the file. I was using NPM only to find you've decided not to publish there (which I think is crazy). I needed the latest version so that Following on from this request for CDNJS you should also be aware that the unpkg option does pull from NPM. So, if publishing to CDNJS is going to take a while to sort, please just publish one more version to NPM so I can use LibMan consistently in the mean time. I just went to check if LibMan had any plans to support aspnet CDN only to find this where someone is having the exact same issue as me (ah it's bchavez): aspnet/LibraryManager#67 (comment) EDIT: again here: https://stackoverflow.com/questions/52091425/how-do-i-use-microsoft-jquery-unobtrusive-ajax-with-libman-library-manager-asp |
@Eilon @mkArtakMSFT This is on PR in the cdnjs repo |
@javiercn the reviewer requested some changes |
@javiercn, please update your PR as requested by the re viewers. |
This was done |
See aspnet/jquery-validation-unobtrusive#76 for info.
The text was updated successfully, but these errors were encountered: