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

wzrd.in service does not work #302

Closed
mostafa opened this issue Jan 19, 2019 · 14 comments
Closed

wzrd.in service does not work #302

mostafa opened this issue Jan 19, 2019 · 14 comments

Comments

@mostafa
Copy link

mostafa commented Jan 19, 2019

Build on the wzrd.in website seems not to work, because the whole server timed out! And building the package using browserify.js also does not produce a firm result and does not work.

@mostafa
Copy link
Author

mostafa commented Jan 19, 2019

A viable option would be to use unpkg service instead: https://unpkg.com/node-uuid@1.4.8/uuid.js

@jimaek
Copy link

jimaek commented Jan 19, 2019

jsDelivr also minifies the files along many other features https://cdn.jsdelivr.net/npm/node-uuid@1.4.8/uuid.min.js

@Annis-Monadjem
Copy link

Annis-Monadjem commented Feb 22, 2019

@mostafa: I'm interested in uuid version 4. Will your suggestion above: https://cdn.jsdelivr.net/npm/node-uuid@1.4.8/uuid.min.js produce uuidv4?

@jimaek: I'm interested in uuid version 4. Will your suggestion above: https://cdn.jsdelivr.net/npm/node-uuid@1.4.8/uuid.min.js produce uuidv4?

At present wzrd.in is crushing uuid/v4 which i'v been using with browserify.

@kj2res
Copy link

kj2res commented Feb 25, 2019

@Annis-Monadjem Yes, you can use uuidv4.

Simply do uuid.v4();

@mostafa
Copy link
Author

mostafa commented Feb 27, 2019

@mostafa: I'm interested in uuid version 4. Will your suggestion above: https://cdn.jsdelivr.net/npm/node-uuid@1.4.8/uuid.min.js produce uuidv4?

@jimaek: I'm interested in uuid version 4. Will your suggestion above: https://cdn.jsdelivr.net/npm/node-uuid@1.4.8/uuid.min.js produce uuidv4?

At present wzrd.in is crushing uuid/v4 which i'v been using with browserify.

It will, since I used and tested it. You can simply load it via an HTML boilerplate and try the console to inspect the uuid object.

@Annis-Monadjem
Copy link

What i finally did was:

  1. $>yarn add uuid
  2. In .js file:
    import uuidv4 from 'uuid/v4'

Thanks @mostafa @trs-king

@mostafa
Copy link
Author

mostafa commented Mar 1, 2019

@Annis-Monadjem This jsdelivr link is for cases where you don't have any packer/bundler and are using browser javascript.

@onlyanegg
Copy link

I'm also having problems with wzrd.in. I'm getting redirected to https, and then I'm getting a 502. I tried it yesterday and got the same result.

@UkrainianCitizen
Copy link

UkrainianCitizen commented Aug 24, 2019

So is this going somewhere? This library was referenced in a JS course and all people including myself can't use browser-ready versions because of the bad gateway error on wzrd.in.

ctavan added a commit to ctavan/node-uuid that referenced this issue Aug 26, 2019
The service wzrd.in seems to be unmaintained for over a year now, see
browserify/wzrd.in@2f7ea69

It currently throws 502 errors on all packages as reported in
uuidjs#302 or
https://talk.observablehq.com/t/wzrd-in-alternatives/571

As stated in
uuidjs#293 (comment)
there are no plans to support legacy bundlers.

Instead, we may consider to go for properly standardized ES6 modules in
the future as has been teased in uuidjs#317

However for the time being let's at least remove these broken
instructions from the README.

Closes uuidjs#176, uuidjs#302
@ctavan
Copy link
Member

ctavan commented Aug 26, 2019

@UkrainianCitizen as mentioned in #176 this is not something the maintainers of this module can change since apparently the service wzrd.in is generally down for over a year.

Please get in touch with the authors of your JS course in order to update the course material to use services that are still up and running.

If you need something that works at this point in time you can try including the following instead in your JS course HTML page:

<script src="https://bundle.run/uuid@latest?name=uuid"></script>

It will make the uuid library available under window.uuid and you can then call window.uuid.v4() or window.uuid.v1().

⚠️WARNING 1 ⚠️: Please be aware that this is something that may be useful for educational purposes but definitely not for any production application!

⚠️WARNING 2 ⚠️: Please also bear in mind that this is not something the authors of this library will provide any official support for in the future!

@UkrainianCitizen
Copy link

UkrainianCitizen commented Aug 27, 2019

@ctavan Thanks for the timely response. Ofc wzrd.in has nothing to do with your library, but what you can do is to host the code on another place if you do provide browser-ready versions for the public. And thanks for your pieces of advice. I never said that there is no workaround, there are many. The author, of course, did give an update on the situation: what I and hundreds of other people have done is adding the code from the original js file as a part of the course projects.

P.S. I am fully aware of things you stated in your warnings.

broofa pushed a commit that referenced this issue Sep 1, 2019
* chore(doc): re-generate README

* fix(doc): remove wzrd.in instruction from README

The service wzrd.in seems to be unmaintained for over a year now, see
browserify/wzrd.in@2f7ea69

It currently throws 502 errors on all packages as reported in
#302 or
https://talk.observablehq.com/t/wzrd-in-alternatives/571

As stated in
#293 (comment)
there are no plans to support legacy bundlers.

Instead, we may consider to go for properly standardized ES6 modules in
the future as has been teased in #317

However for the time being let's at least remove these broken
instructions from the README.

Closes #176, #302
@ctavan
Copy link
Member

ctavan commented Sep 19, 2019

This has been resolved through #323

@ctavan
Copy link
Member

ctavan commented Feb 24, 2020

We have just released uuid@7.0.0 which now features direct UMD builds again: https://github.com/uuidjs/uuid#umd-builds

Please feel free to open a new issue if you encounter any issues with the new version.

@poorna029
Copy link

@Annis-Monadjem Yes, you can use uuidv4.

Simply do uuid.v4();

hey it is working.

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

No branches or pull requests

8 participants