Closed VivekShah1983 closed 7 years ago
I'm having a hard time following this. It looks like you aren't using our library correctly but are trying to use it like the system builder library. The two are very different. @ahmedshuhel
As Rob said it's hard to follow. Could you create a GitHub repo reproducing this behavior?On Dec 8, 2016 9:35 AM, Rob Eisenberg notifications@github.com wrote:I'm having a hard time following this. It looks like you aren't using our library correctly but are trying to use it like the system builder library. The two are very different. @ahmedshuhel
—You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or mute the thread.
I'm submitting a bug report
Please tell us about your environment:
Operating System: Windows server 2012 R2
Node Version: 4.4.1
NPM Version: 3.5.3
JSPM OR Webpack AND Version JSPM 0.16.30
Browser: all
Language: all
Current behavior: If I have jspm based sytemjs config as shown below, and i create a bundler expression like below package1 - package2
It throws error saying package.js is not present. Can you please guide me how to resolve this issue System.config({ baseURL: "/", defaultJSExtensions: true, transpiler: false, paths: { "npm:": "jspm_packages/npm/" },
map: { "package1": "npm:package1@1.0.0", "npm:package1@1.0.0": { "package2": "npm:package2@1.0.0" } } });
Expected/desired behavior:
What is the expected behavior?
What is the motivation / use case for changing the behavior?