Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Run in browser #16

Closed
8 tasks done
maxkoryukov opened this issue Jan 22, 2017 · 4 comments
Closed
8 tasks done

Run in browser #16

maxkoryukov opened this issue Jan 22, 2017 · 4 comments
Assignees
@maxkoryukov
Labels
blocked enhancement
Milestone
0.3.0 browser ver...

Comments

@maxkoryukov
Copy link
Contributor

maxkoryukov commented Jan 22, 2017 •
edited
Loading

Allow to run SDK in browser

  • gulp automation
  • packing tool
  • package-format
    • use bower???
    • where to store browser-ready version.
  • provide webpack-compatible version of route4me-node (just check)
  • run tests in browser - will be solved in Tests in browser #49
  • connect to saucelabs or similar (browserstack) to test in 5 most used browsers - will be solved in Tests in browser #49
@maxkoryukov maxkoryukov mentioned this issue Jan 22, 2017
Closed
27 tasks
maxkoryukov added a commit to maxkoryukov/route4me-nodejs-sdk that referenced this issue Jan 24, 2017
@maxkoryukov
A bunch of improvements
affb023 
* Documentation improved ( see route4me#17 )
* One step closer to browser version, by removing `os` dependency (fix #4) (see route4me#16)
* Validation of input and output for/from API will be provided by external module, and could be configured additionally
* Log calls unified (passing only objects)
maxkoryukov added a commit to maxkoryukov/route4me-nodejs-sdk that referenced this issue Jan 25, 2017
@maxkoryukov
gulp-linting enabled, now it is much simpler to develop
e030604 
see route4me#16 - one step closer
@maxkoryukov maxkoryukov modified the milestone: 1.1.0 docs and improvements Jan 27, 2017
@maxkoryukov maxkoryukov mentioned this issue Jan 29, 2017
Closed
@maxkoryukov maxkoryukov modified the milestones: 1.2.0 make the lib better, 1.1.0 docs and improvements Feb 5, 2017
@maxkoryukov maxkoryukov self-assigned this Feb 21, 2017
@maxkoryukov
Copy link
Contributor Author

Bower NO

NO BOWER. Plz, don't use bower.

@maxkoryukov maxkoryukov mentioned this issue Feb 22, 2017
Open
@maxkoryukov
Copy link
Contributor Author

Temporary blocked by #48

@maxkoryukov
Copy link
Contributor Author

WebPack uses the concept of targets and provides module resolution rules (https://webpack.js.org/concepts/module-resolution/)

Module resolution depends on target, but always checks fields in package.json :

  • target web : fields browser, module, main
  • target node: fields module, main

So, when the package is used as

  • pure Node package - main will be used
  • by WebPack - browser or module will be used (depending on target)
  • by browser - browser version will be used

BTW: for published on NPM version we will get the public CDN: https://unpkg.com/

@maxkoryukov
Copy link
Contributor Author

Route4Me-User-Agent

maxkoryukov added a commit that referenced this issue Feb 22, 2017
@maxkoryukov
Toolchain for building browser version
a8c554d 
see #16
@maxkoryukov maxkoryukov mentioned this issue Feb 28, 2017
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@maxkoryukov maxkoryukov

Labels
blocked enhancement
Projects
None yet
Milestone
0.3.0 browser version + clear doc
Development

No branches or pull requests
1 participant
@maxkoryukov