Add TypeScript Framework Variants and Repository Restructure #51
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… and assets path, makes loadNutrient util async
…lid and solid start
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Moved frontend frameworks to
/frameworksdirectory from/examples. I'm totally willing to discuss a different name, location for this, but I thought overall that the frontend frameworks might want their own directory.Adds all new examples for each frontend framework, with routing for different pages.
Each framework example now has TypeScript and JavaScript equivalents.
Adds SolidJS support
Adds example for Vanilla JS and TS
Each framework has its own (identical) nutrient directory with examples written in typescript or javascript. This is intentional. It makes more sense for them to all share (now), but down the road, I think each framework should have its own implementations so we can start using framework specific methods as opposed to all the example implementations being written in vanilla javascript/typescript.