Make front-end templates more idiomatic
See original GitHub issueRight now the front-end templates used by create-near-app aren’t very idiomatic. It would be nice to improve this by creating libraries for each front-end framework like https://www.npmjs.com/package/near-react-hooks.
This has two major advantages:
- the developer experience is much better as the NEAR code fits in better with the chosen framework
- it will be easier to incorporate NEAR into existing applications by using the framework specific library directly.
If this is of interest I’d be happy to update the current react template to use near-react-hooks. Also I can work on creating an angular service library and a vue plugin.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Layouts | Bridgetown
Layouts are templates that wrap around your resource's content. They allow you to have the source code for your template in one place...
Read more >foolin/goview - GitHub
Goview is a lightweight, minimalist and idiomatic template library based on ... Multiple Engine - Support multiple templates for frontend and backend.
Read more >Do web developers prefer to work from templates or code from ...
I'm going to assume you're talking about front-end. Most developers have at least some sort of 'base code' that they use as a...
Read more >templating - renderTemplate in a plugin for front end request ...
Digging a little more into this. If I pass a path for a template that doesn't exist I get an error message "Unable...
Read more >10 Websites To Practice Your Frontend Development Skills
That's why in this article, we have gathered a list of 10 great websites where you can practice front-end development skills!
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Nice! ok i see the vision now. Seems legit to me!
I’m with you that near-api-js needs to support better code completion & inline documentation. And I agree that the use of
windowvariables is unusual. (As an aside, for TypeScript projects there is a way around the lack of code completion withwindowvariables: create awindow.d.tsfile. It seems like this would add potential errors to a generated JS project though, and would add cognitive overhead for developers in any case.)Here are some ideas that will guide upcoming improvements to near-api-js; I’d love to get your thoughts: https://github.com/near-examples/guest-book/pull/161
I believe that this would also accomplish our shared goals of great code-completion and removing
windowdependencies.