https://github.com/tn1ck/anagrams.io

Sophisticated anagrams finder. Lets you explore the whole anagrams search space. Multi language support: english, german, french, spanish
https://github.com/tn1ck/anagrams.io

anagram anagram-finder anagram-solver anagrams anagrams-search

Last synced: 6 days ago
JSON representation

Sophisticated anagrams finder. Lets you explore the whole anagrams search space. Multi language support: english, german, french, spanish

• Host: GitHub
• URL: https://github.com/tn1ck/anagrams.io
• Owner: TN1ck
• License: mit
• Created: 2021-06-13T14:17:30.000Z (over 3 years ago)
• Default Branch: master
• Last Pushed: 2024-08-18T13:53:24.000Z (5 months ago)
• Last Synced: 2024-08-18T15:02:42.885Z (5 months ago)
• Topics: anagram, anagram-finder, anagram-solver, anagrams, anagrams-search
• Language: TypeScript
• Homepage: https://anagrams.io
• Size: 42.2 MB
• Stars: 8
• Watchers: 3
• Forks: 3
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# anagrams.io

[Anagrams.io](https://anagrams.io) is a client side anagrams finder. The goal was to make it easy to find good anagrams for any word length.

Due to the calculations happening client side, the whole search space can be explored.

[![Netlify Status](https://api.netlify.com/api/v1/badges/09b49293-2071-4ea9-b59a-dc569e40c53c/deploy-status)](https://app.netlify.com/sites/anagramsio/deploys)

[anagrams.io-preview.webm](https://github.com/TN1ck/anagrams.io/assets/2116347/e28fd65e-9f56-469f-b6bf-cb462f9e8fd7)

## Getting started

1. To run it you need node.js, see their guides on [how to install](https://nodejs.dev/en/learn/how-to-install-nodejs/).

2. Run `npm install`

3. Run `npm start` for local development

4. Run `npm build` to create the production build in the `dist` folder. Use `npm run preview` to preview it.

## Technologies

The project is quite old and is using some technologies I wouldn't use now, but it works.

1. React for the UI. This was written before hooks were a thing so component lifecycle is mostly done with classes and usage of now deprecated functionality.

2. mobx for state management. The state manipulations are quite complex as we have to deal with a lot of anagrams calculated per second and want to keep it performant.

3. Styled components for theming. It's not super consistent, there also inline styles here and there.

4. Netlify for deployment.

## Contributing

Fork & Make a pull request! Any contributions are welcome (especially improving the dictionaries).