[incomplete] Browser support #105
Closed
Conversation
This file contains 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
This causes some tests to time out instead of kill seneca. the [process shim](https://www.npmjs.com/package/process) only exists to provide the nextTick method. the ultimate reason is still rjrodger/use-plugin#4
all of these tests are broken by this issue in use-plugin: rjrodger/use-plugin#4 once a viable fix is available, they should be enabled one-by-one and tested again.
The browser environment requires global functions be called with null as their context.
|
can you share your motivation for running seneca in the browser? |
|
@juliangruber just an experiment to see if it is possible :) |
|
daydreaming would it be possible to use seneca with web-workers? The web workers API is in strings, and seneca communicates through JSON... maybe even hook in to local storage for data entities? I'm not sure it needs to be within this project, but I like the abstractions seneca provides, and would like something nicer than web workers. Maybe we can just make that seneca-the-younger ;) |
|
closing as won't fix. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I took a stab at getting seneca to run in the browser, by using browserify to generate a standalone package in UMD format that can be used either directly in the browser, or by require.js or browserify itself. It is automatically generated on publishing to npm, and running npm install. You can then just add a script for the seneca.browser.js file.
The process I followed was to use zuul to run the mocha tests in the browser environment, and make the changes to get as many of them running. You can run
npm run-script test-browser, and go tohttp://localhost:8080/__zuulto run them yourself.More information is available in each of the commits, but the big roadblock in all of this is that use-plugin is really incompatible with the browser. Most of the functionality of seneca drives through that module, so anything that does seneca.act or seneca.use is broken until it's rewritten.