You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 17, 2019. It is now read-only.
I find that the current version of fusion.js is merely made for React SSR app, that I can only access the entry point by some hidden logic under fusion-cli's entry file. As u illustrated in code of L29 it is designed for some FUSION_ENTRY_PATH entry, which is also used by node hot server.
Here, I got one situation that only require the bundled React logic(for some jssdk). Is that possible to integrate the fusion independent of fusion-cli? That is
Current behavior
importAppfrom'fusion-react';importRouterfrom'fusion-plugin-react-router';constapp=newApp(root);app.register(Router);// I add this line: https://github.com/fusionjs/fusion-cli/blob/master/entries/client-entry.js#L29app.callback().call();
Expected behavior
// Could I shorten the calling process to this in my sdk?constapp=newApp(root);app.register(Router);
The text was updated successfully, but these errors were encountered:
wheelo
changed the title
How to make a "serverless" fusion app with the strip of node.js?
How to make a "serverless" fusion app with the stripping of node.js?
Oct 23, 2018
Thank you for filing a bug report. I think this is possible today, but also quite hacky. You can construct a HTML file and pull in the .fusion/ generated scripts manually. I think we would need to do a lot of work to fully support applications without a server, but it could be possible with time.
Curious about your usecase, why don't you want to use a server?
@KevinGrandon Currently, the server api is provided solely by some Java server, and we put the static javascript file and some HTMLs in nginx static server
Type of issue
Feature request
Description
I find that the current version of fusion.js is merely made for React SSR app, that I can only access the entry point by some hidden logic under fusion-cli's entry file. As u illustrated in code of L29 it is designed for some FUSION_ENTRY_PATH entry, which is also used by node hot server.
Here, I got one situation that only require the bundled React logic(for some jssdk). Is that possible to integrate the fusion independent of fusion-cli? That is
Current behavior
Expected behavior
The text was updated successfully, but these errors were encountered: