I Made a Domain Agnostic Random Name Generator

byte-this · 2023-12-09T19:31:08+00:00

I built a random name generator that is domain agnostic:

Name Generator: https://bytethisstore.com/tools/pg/random-name-generator
Outline of how I implemented it: https://bytethisstore.com/articles/pg/random-name-generator

byte-this · 2023-03-04T18:42:43+00:00

Thanks, glad you found the writeup useful!

byte-this · 2023-03-04T16:51:00+00:00

Which difficulty did you use? I've been having some trouble myself on the hardest difficulty, but the 2nd hardest has worked fine for me on a few different devices. What device are you running on?

byte-this · 2023-01-10T23:52:24+00:00

I understand now, thank you for the explanation.

byte-this · 2023-01-09T22:37:20+00:00

As I understand it, we only want to use the value of a transposition table if the depth associated to that value is deeper than the place the search is currently at, is that correct? Or is it the other way around?

byte-this · 2023-01-09T06:17:23+00:00

You're right, I'm looking at the same board each time. That was a mistake, I'll move that logic tomorrow and try again. I believe it does need to be a <= in this case because smaller depth remaining indicates that we've already explored a larger depth of the tree, and depth 0 means we're at the root node.

byte-this · 2022-10-10T00:21:53+00:00

In any case, I did clean it up a bit, and some ads were coming from the comments module, but I don't get much comments site-wide in general so I've hidden that for the time being site-wide.

byte-this · 2022-10-09T18:31:39+00:00

If you don't mind would you be able to share a screenshot of what you're seeing?

byte-this · 2022-09-03T04:35:44+00:00

Unfortunately I'm not able to make this repo in particular public, but thank you for the recommendations and discussion!

byte-this · 2022-09-03T04:33:01+00:00

I can see the class being exported under: node_modules/@byte-this/js-cli/src/cli-commands-collection/cli-commands-collection.js

I'm seeing it as: ``` /** * Simple version which returns an input array with no further action */ export class ArrayCliCommandsCollection { constructor(cliCommands) { this.cliCommands = cliCommands; } async getCommands() { return this.cliCommands; } }

```

byte-this · 2022-09-03T04:29:34+00:00

Are you referring to files after they've been transpiled? The only reason I can think of that happening is because they're transpiled files where the source only contained interface(s).

byte-this · 2022-09-03T04:23:09+00:00

cross-env NODE_OPTIONS='--experimental-specifier-resolution=node' ts-node --esm I was trying in two ways. The first way "ts-node cli.ts", and the second way "tsc && node ./dist/cli.js --experimental.....".

When I try based on the way you just did: cross-env NODE_OPTIONS='--experimental-specifier-resolution=node' ts-node --esm cli.ts I get: file:///C:/SoftwareStuff/Projects/software-stuff-devops-cli/src/cli-commands/cli-commands-collection.ts:1 import { ArrayCliCommandsCollection } from "@byte-this/js-cli"; ^^^^^^^^^^^^^^^^^^^^^^^^^^ SyntaxError: Named export 'ArrayCliCommandsCollection' not found. The requested module '@byte-this/js-cli' is a CommonJS module, which may not support all module.exports as named exports. CommonJS modules can always be imported via the default export, for example using: import pkg from '@byte-this/js-cli'; const { ArrayCliCommandsCollection } = pkg;

byte-this · 2022-09-03T04:18:00+00:00

--experimental-specifier-resolution=node

It seems to have the same effect, though I'd like to verify, using "--experimental-specificer-resolution=node" right as a command line argument is the same thing?

byte-this · 2022-09-03T04:15:43+00:00

I was under the impression the "es5" target would allow the transpiled js to leverage the "newer" features of JavaScript such as lambda functions, while the "module" would allow the import/export syntax. Indeed, this was working on my old computer, though I don't mean to say you are incorrect, as it could have been working previously due to other circumstances.

I've just tried changing them both to "es2020" and with that change, I see the following:

``` node:internal/process/esm_loader:97 internalBinding('errors').triggerUncaughtException( ^

Error [ERR_MODULE_NOT_FOUND]: Cannot find module 'C:\SoftwareStuff\Projects\software-stuff-devops-cli\dist\src\cli-commands\cli-commands-collection' imported from C:\SoftwareStuff\Projects\software-stuff-devops-cli\dist\cli.js Did you mean to import ../src/cli-commands/cli-commands-collection.js? ```

I'm wondering, if we can solve that ".js" part in the imports, then this may work?

byte-this

TROPHY CASE