Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Dec 04 05:50

    guybedford on master

    updates (compare)

  • Dec 02 00:28
    mclizz closed #178
  • Dec 02 00:27
    mclizz opened #178
  • Nov 22 21:20
    nosideeffects commented #46
  • Nov 22 20:31
    guybedford commented #46
  • Nov 22 19:32
    nosideeffects commented #46
  • Oct 16 06:33
    AmazingDesign commented #85
  • Sep 11 12:48
    ionutss opened #177
  • Aug 23 13:42
    amenadiel commented #85
  • Aug 23 13:37
    amenadiel commented #85
  • Aug 23 13:37
    amenadiel commented #85
  • 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
Guy Bedford
@guybedford
import maps mean users only re-fetch those boundaries that change
team-a deploying daily, doesnt mean all vendor chunks have to be updated daily
team-a deploying daily just means team-a optimized package gets updated daily
but everything else stays the same
(and remains cached in browser)
csr632
@csr632
Thanks for the awesome explanation of optimized package! This idea makes my mental model much more clear.
This idea should be documented somewhere. I would love to refine my demo repo to demonstrate this idea.
Guy Bedford
@guybedford
glad it makes sense, yes I definitely want to highlight this concept with this next update (which includes some extra features for package optimization), will bear that in mind
csr632
@csr632
I have refined my demo repo to demonstrate how to use systemJS to achieve front-end microservices.
csr632
@csr632
image.png
I am now looking for a development workflow, but I can't figure out how jspm link works(jspm link [<name>] <source>)
Does it behave like npm link?
Does it do dew transform?
What dose that error message mean?
Guy Bedford
@guybedford
@csr632 jspm link expects the form - jspm link npm:pkg@version ../path
I’ve been working on linking workflows in the latest version upgrade quite a bit
Will make this much simpler
If the package.json of the linked folder contains a “name”, “version” and “registry” field that should be enough to avoid the message
I’ve removed the need for the “registry” field in the latest version, defaulting to np@
*npm
csr632
@csr632
jspm install is not installing jspm.dependencies(listed in package.json) recursively, is this intended?
csr632
@csr632
For example, run jspm install @micro-frontend-demo/team-b@1.0.0. I expect @micro-frontend-demo/shared-lib1 to be installed, because it is listed in @micro-frontend-demo/team-b@1.0.0's package.json->jspm.dependencies
csr632
@csr632
Ok I guess this is imitating behaviour of npm.
Can jspm provide low-level api to install a package without updating package.json?
Also, can jspm provide low-level api to install a package without recursively installing its dependencies?
These would be helpful for tool-developing.
Joe Pea
@trusktr
@csr632 It's been a while, but I would imagine jspm might have an CLI option not to save or update package.json.
@guybedford Does jspm.io multiplex modules over HTTP/2?
Dilip Kr. Shukla
@fusionstrings

@fusionstrings it doesn't need to be released unflagged, but some of the major decisions like whether "mode": "esm" will be supported (nodejs/node#18392) are important to ensure consistency.

Congratulations @guybedford and many thanks for your resolve and push for right way even though it means waiting.
https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V13.md#13.2.0

Dilip Kr. Shukla
@fusionstrings

in short, if you will really miss the ability to do jspm map && http-server and have all of npm run unbuilt in the browser now is the time to shout :)

I am late in party but I do use this workflow, and I would miss it.

Guy Bedford
@guybedford
@fusionstrings to explain the details a bit more clearly:
  1. This workflow will still work if all packages you use are ES modules, the problem only applies to CommonJS
  2. If you have CommonJS, you will still be able to get this workflow against the jspm CDN (jspm map --cdn && http-server would work)
  3. So it just wouldn't work offline with CommonJS
Dilip Kr. Shukla
@fusionstrings
How to I use PR beta 8 for local jspm?
Dilip Kr. Shukla
@fusionstrings

@fusionstrings to explain the details a bit more clearly:

  1. This workflow will still work if all packages you use are ES modules, the problem only applies to CommonJS
  2. If you have CommonJS, you will still be able to get this workflow against the jspm CDN (jspm map --cdn && http-server would work)
  3. So it just wouldn't work offline with CommonJS

Thanks @guybedford

Dilip Kr. Shukla
@fusionstrings
At the moment I am having trouble running PR8 for my local jspm jspm/jspm-cli#2496
I am facing multiple problems. What is th eprocess if anyone have done it
Dilip Kr. Shukla
@fusionstrings
While doing npm link and npm run build, I get following

fs.js:440
  handleErrorFromBinding(ctx);
  ^

Error: ENOTDIR: not a directory, open '/Users/dilip/github/jspm/jspm-cli/lib/api.js/package.json'
Guy Bedford
@guybedford
The jspm build workflow is still being finalized on that PR
If you can post that bug that would help @fusionstrings
The PR still needs updates to jspm build and then also to jspm map to support the browser CDN dev workflow
I expect those changes to be in Jan / Feb
I de-prioritized that work since there’s not enough users to justify shipping (there is no positive feedback to shipping for me)
So I’m rather just doing things in my own order to get it done by March
Right now I’m working on the next iteration of the CDN significantly improving the latency and bandwidth by precomputing an optimization of the entire npm registry to the CDN
Yes, that means pre-processing 7TB of packages
Should have that up for first week of Jan
Dilip Kr. Shukla
@fusionstrings

Thanks, I will file the bug but I wanted know know first what is the flow to use unrelease version of jspm.
I have been working on (preparing) adopting JSPM for production but since lots of issues which is parft of the PR I am kind of blocked to proceed. If I can get the PR branch working on my local, it will be very helpful in trying out and feedback.

I posted here thinking it is more swift communication / feedback.

I also want to generate and inject import map from serverside using jspm js API.

Guy Bedford
@guybedford
The PR is incomplete so I would not suggest using it currently.
For generating import maps through the API look at the jspm CLI JS file - all CLI operations wrap the jspk API and can also be accessed through a require of jspm following the same sort of patterns
Improving the API is definitely something that can be done too
My priority as I said is on the next CDN version right now, so the PR / next release won’t be merged until Jan
It’s costing a lot of compute to do an optimization of the entire npm registry and I am able to spend $1000’s of dollars of Google cloud free compute on this
But the compute expires at the end of the month so that is why this is my current priority entirely
(Along with my first holiday in a long time lol)
Dilip Kr. Shukla
@fusionstrings
Thanks for sharing. You should infact priortise the holiday over anything.
I will use beta 7 then. Is there any way I can atleast use latest jspm resolve with beta 7 release?
Guy Bedford
@guybedford
Updating the resolver against master should work I think, but I haven’t tested it out
Dilip Kr. Shukla
@fusionstrings

Updating the resolver against master should work I think, but I haven’t tested it out

Thanks