-
Notifications
You must be signed in to change notification settings - Fork 151
Future plans #14
Comments
Thanks for asking. We will add a roadmap to the wiki soon. I think your question is more related to ES6? If you are using typescript you can do imports today because typescript abstracts away the module resolution logic and lets you decide this at compile/transpile time. If you are using javascript you can't do import directly as the library is on ES5. Instead you would have to use require.js to do the module resolution. If you really want to have ES6 modules and not depend on any external module libraries you can build the sdk yourself by targeting ES6. Just change the build task to target ES6 instead. |
I am in a typescript project(Angular) and when trying to import the module, there is an error stating that the file is not a module |
I would have expected that to work. Let me write up a working sample and I will share that with you. |
Any sort of update on this issue, or when it might get an update? |
We are looking into this and will provide an update next week, |
Thanks for looking into this Rav, is there any kind of issue that came up in trying to resolve this? |
Is this repo the only official Microsoft SDK for Javascript? Is there a CDN anywhere hosting the SDK? |
Any chance of getting an update on this issue? Thanks! |
Yes currently this is the only source. Thanks for feedback on CDN. We don't have plans on hosting in CDN currently. |
Thanks, but i meant the original issue of this library supporting import statements that was being supported by RaviPidaparthi |
Sorry we do not have support currently. We plan to have angularjs support in a future release. |
Its not just angularJs support, the ability to import a project using var package = require('package') would allow usage for any javascript frameworks including react, angularjs, and several more. My question ended up being when require will be supported as depicted in the image on post #3 |
look @ #52 |
Is there a roadmap for this project? Also, will this be adapted to allow import statements to work?
ex:
import {SDK} from 'microsoft-speech-browser-sdk';
The text was updated successfully, but these errors were encountered: