## Where communities thrive

• Join over 1.5M+ people
• Join over 100K+ communities
• Free without limits
##### Activity
• Aug 23 13:42
• Aug 23 13:37
• Aug 23 13:37
• Aug 12 14:16
itaybiri opened #51
• Jul 25 19:43
guybedford commented #49
• Jul 25 19:26
fusionstrings closed #49
• Jul 25 19:26
fusionstrings commented #49
• Jul 25 04:47
guybedford edited #50
• Jul 25 04:11
guybedford closed #44
• Jul 25 04:11
guybedford commented #44
• Jul 25 04:11
guybedford opened #50
• Jul 24 00:39
priyabrat1801 closed #176
• Jul 24 00:39
priyabrat1801 commented #176
• Jul 24 00:39
priyabrat1801 commented #176
• Jul 23 23:59
guybedford commented #176
• Jul 23 23:33
priyabrat1801 commented #176
• Jul 23 22:51
guybedford commented #44
• Jul 23 22:49
guybedford commented #49
• Jul 23 22:40
guybedford commented #176
• Jul 23 22:37
guybedford commented #176
Josiah Haswell
@josiahhaswell
Is there a sane way of bundling RxJS with JSPM?
Chris Lane
@ChrisLane
I seem to get longer and longer build times the longer I use jspm bundle src/js/main.js -wid, is this a known issue?
Sometimes it'll take about 10 seconds to build, sometimes minutes
Chris Lane
@ChrisLane
No suggestions then D:
Chris Lane
@ChrisLane
JSPM crashes with an out of memory error after a while of that, suspect that's a possible cause for the slowness. JSPM 0.17
Josiah Haswell
@josiahhaswell
@ChrisLane Hmm. Have you tried increasing the node max memory limit?
@ChrisLane It's probably a bug, but that might be a workaround
Chris Lane
@ChrisLane
@josiahhaswell Well yes, increasing the max memory limit would certainly be a workaround for any memory leak but it's not a good one.
Guy Bedford
@guybedford
@all the jspm 2.0 beta has been released at https://jspm.org.
Dilip Kr. Shukla
@fusionstrings
@guybedford That's so awesome, thanks a ton :D
Guy Bedford
@guybedford
Thank you for all the feedback and support! Was quite a process.
Dilip Kr. Shukla
@fusionstrings

Yeah, from guides, documentation, sandbox, CDN to ACTUALLY getting "modules" in node. I don't know how much more.

I would say you contributed to make impossible possible. I didn't have hope to get js extension in node for esm., until you showed up 🤗

Guy Bedford
@guybedford
It was a lot of work all around! Building consensus in the Node modules group took a year, but we got there! We nearly got named exports for CommonJS too but unfortunately that’s fallen short. There maybe alternatives though like jspm supports ‘namedExports’ field in package.json to define the list of named exports per module (object with module path as key, array of exports as value). We may or may not get that into Node too. Keep those issues coming :)
Dilip Kr. Shukla
@fusionstrings
Sure, I've started my test run from today :)
Toby Ealden
@TobyEalden
A couple of things I'm not clear about w.r.t jspm 2.0 beta - the need to specify the index.js, e.g. import Button from '@material-ui/core/Button/index.js'; and then subsequently the need to explicitly reference the default export, e.g. React.createElement(Button.default, .... I understand the workings behind the scenes, but is there a way (or a plan) to do this auto-magically as was the case in v0.17 ?
Guy Bedford
@guybedford
@TobyEalden the rule is that how it works in node --experimental-modules is how it works in jspm 2, and this is for ecosystem compatibility
handling of the default export has been a big technical debt of Babel ES modules
that we will all have to go through in the transition to node ES modules
jspm 2 brings you that pain, today!
yay
:P but if you start working torwards code that runs this way, you'll find future transition in Node.js ecosystem much easier, and will be a major problem for all of us yes
There are two things that make this easier through config:
1. map configuration in package.json - { "map": { "./Button": "./Button/index.js" }
1. named exports configuration in package.json: { "namedExports": { "./Button/index.js": ["named", "exports"] } }
Unfortunately named exports configuration won't apply to this case because in this scenario it's about the .default.default not named exports
Post PRs and bugs to libraries, and get them to fix these things is effectively the long slow painful process we need to go through
Node.js won't be able to dance around this stuff, so we should't try to either, otherwise compat issues just compound
(and it could be argued it was approaches like in previous jspm that led to this problem in the first place)
healthy ecosystems FTW. Help sharing these principles is needed.
Guy Bedford
@guybedford
Btw both of the above configs can be set via overrides in jspm 2 - jspm install @material-ui/core -o map['./Button']='./Button/index.js' sort of thing
also if a package has ES modules you can override all that with jspm install some-pkg -o type=module main=dist/es-main.js
although that probably won't work either due to the above compatibility issues
basically, no one is using ES modules right :P
we will fix that though, just slowly
For further discussion, I'm online much more frequently on the Discord chat - https://discord.gg/rUg8u8
Toby Ealden
@TobyEalden
OK, understood - thanks for the explanation
Craig Shearer
@craigsh
I'm back on jspm version 0.16.48, and still using it to run bundle-sfx --minify. I've just upgraded node to the latest LTS version (10.15.3) but now jspm bundle-sfx crashes with the following:
jspm[16972]: c:\ws\src\node_contextify.cc:626: Assertion args[1]->IsString()' failed.
1: 00007FF6D7D2F04A v8::internal::GCIdleTimeHandler::GCIdleTimeHandler+5114
2: 00007FF6D7D0A0C6 node::MakeCallback+4518
3: 00007FF6D7D0A17F node::MakeCallback+4703
4: 00007FF6D7CDF630 node::DecodeWrite+13024
5: 00007FF6D850C122 v8::internal::OptimizingCompileDispatcher::Unblock+59890
6: 00007FF6D850D289 v8::internal::OptimizingCompileDispatcher::Unblock+64345
7: 00007FF6D850C5CC v8::internal::OptimizingCompileDispatcher::Unblock+61084
8: 00007FF6D850C4EB v8::internal::OptimizingCompileDispatcher::Unblock+60859
9: 000001113D75C5C1
Any ideas what I can do to fix this apart from downgrading node?
Guy Bedford
@guybedford
Interesting, I’ll take a look and see if I can post a Node.js bug or change the function call. It’s an argument validation failure in the Node C++ code so should be possible to track down that way. If you can share a full replication repo that would help.
Craig Shearer
@craigsh
@guybedford thanks for the willingness to help. Unfortunately it's a fairly huge private repo that I'm not able to share. I'll see if I can put together a small reproducer.
Craig Shearer
@craigsh
@guybedford I've managed to resolve this. Seems it wasn't just the build process but jspm crashing. I deleted my node_modules folder and also deleted and regenerated my jspm.config.js file, and now the build works. Whew! :)
Guy Bedford
@guybedford
ah, sounds like a dependency bug that got upgraded. Thanks for the update.
@deap82

Does anyone have any input to why we occasionally run in to this kind of error message when jspm installis run in our build environment;

warn It's taking a long time to process the dependencies of npm:aurelia-templating@1.10.1.
This package may need an ignore property to indicate test or example folders for jspm to skip.

warn Installation changes not saved.
,
err  Error: unexpected end of file
at Gunzip.zlibOnError (zlib.js:153:15)

err  Error: EPERM: operation not permitted, unlink 'C:\agents\2.150.3\.jspm\packages\npm\aurelia-templating@1.10.1\doc\article\en-US\templating-custom-elements.md'

signal: null
status: 1

Stack:
Error: Command failed: jspm install -y

err  Error: unexpected end of file
at Gunzip.zlibOnError (zlib.js:153:15)

err  Error: EPERM: operation not permitted, unlink 'C:\agents\2.150.3\.jspm\packages\npm\aurelia-templating@1.10.1\doc\article\en-US\templating-custom-elements.md'

at checkExecSyncError (child_process.js:601:13)
at Object.execSync (child_process.js:641:13)
at Gulp.Orchestrator._runStep (D:\a\1\s\Vklass\src\node_modules\orchestrator\index.js:214:10)
at Gulp.Orchestrator.start (D:\a\1\s\Vklass\src\node_modules\orchestrator\index.js:134:8)
at runNextSet (D:\a\1\s\Vklass\src\node_modules\run-sequence\index.js:124:15)
at runSequence (D:\a\1\s\Vklass\src\node_modules\run-sequence\index.js:136:2)
at Gulp.Orchestrator._runStep (D:\a\1\s\Vklass\src\node_modules\orchestrator\index.js:214:10)
at D:\a\1\s\Vklass\src\node_modules\orchestrator\index.js:279:18
at <anonymous>
##[error]Gulp failed with error: C:\npm\prefix\gulp.cmd failed with return code: 1

When I check my local .jspm folder and the package aurelia-templating-resources@1.10.1 it only has these files (screenshot above).

So what is this file ('C:\agents\2.150.3.jspm\packages\npm\aurelia-templating@1.10.1\doc\article\en-US\templating-custom-elements.md') even doing in the build environment?

Chris Lane
@ChrisLane
Seems like the memory leak I found a while ago occurs when using --inject in 0.17
Alex
@SuicidalTissue
Having some issues with github rate limits and seem to be getting this when trying to configure a token, any ideas?
ubuntu@ip-172-96-147-181:~\$ jspm registry config github
warn (jspm) registries.github.auth global github registry auth token is not a valid token format.
err (jspm) /usr/lib/node_modules/jspm/node_modules/@jspm/npm/npm.js:303
for await (const chunk of createPublishStream.call(this, pjson, tarStream, { readme, description: pjson.description, tag, access, registryUrlObj })) {
^^^^^

SyntaxError: Unexpected reserved word`
Guy Bedford
@guybedford
@SuicidalTissue which version of jspm are you running there?
DonoZhang
@DonoZhang
Hi everyone, why I had this error when "jspm init"? :
err (jspm) jspm init has not yet been implemented.
And if I installed jspm into the project using --dev mode, I can call "jspm init", but then I still had err : "endpoint.getOverride is not a function"