Open oniseijin opened 7 years ago
Next problem: dependencies: there are many and quite a bit more than what I had to do for basic angular2 support; and, having that npm support within brjs would make this much easier. This isn't even babel or react-templates. react and react-dom:
+-- react@15.4.2 | +-- fbjs@0.8.9 | | +-- core-js@1.2.7 | | +-- isomorphic-fetch@2.2.1 | | | +-- node-fetch@1.6.3 | | | | +-- encoding@0.1.12 | | | | | `-- iconv-lite@0.4.15 | | | | `-- is-stream@1.1.0 | | | `-- whatwg-fetch@2.0.3 | | +-- promise@7.1.1 | | | `-- asap@2.0.5 | | +-- setimmediate@1.0.5 | | `-- ua-parser-js@0.7.12 | +-- loose-envify@1.3.1 | | `-- js-tokens@3.0.1
@oniseijin We've put active BRJS work on hold and are focusing on CT.Next which will is based on npm and webpack. I don't see us doing any npm work in BRJS tbh.
As done in #1681 and #1687 have React JS support. This is mentioned in the Bladerunner js docs as being possible, so, actually doing it would prove a lot and open up more use cases.
This would mean template, unit test, integration test, aspects, blades etc.
Preference is to use React in the same way as knockout/angular, namely the template separate from the code, but this may not be the "React way" and might have only limited support (https://wix.github.io/react-templates/); +JSX support (babel hook)?