wzrd.in service does not work

[mostafa]

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]

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

[jimaek]

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

[Annis-Monadjem]

@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]

@Annis-Monadjem Yes, you can use uuidv4.

Simply do uuid.v4();

[mostafa]

@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]

What i finally did was:

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

Thanks @mostafa @trs-king

[mostafa]

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

[onlyanegg]

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]

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]

@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]

@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.

[ctavan]

This has been resolved through #323

[ctavan]

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]

@Annis-Monadjem Yes, you can use uuidv4.

Simply do uuid.v4();

hey it is working.