Public discussions for the Express.js organization
This repository is used for generalized Express.js discussions.
The Express.js Technical Committee (TC) meets online every other week, providing a live stream of the discussion and a recording of past meetings. Topics for the meetings are determined on an as-needed basis and may be technical or management of nature.
Current meeting schedule: Wednesdays 23:30 UTC
Recordings of past meetings are available on the Express Youtube Channel.
Is there going to be an UberConference for this meeting @mikeal ? If possible, I'd like to dial in today, so pls provide the phone # as well.
The entire community is welcome to tune in and observe the meeting live at the time below. The following people are listed here as explicit invitees to get an email notification about the upcoming meeting:
Invited:
Nov 2, 2016 - 23:30 UTC
YouTube Live
req.next / what should be documented.Invited:
April 20th, 2016 - 23:30 UTC
Google Hangouts:
Link for Participants: https://plus.google.com/hangouts/_/hoaevent/AP36tYdM_bgNKc1pXakhc8lqt_VHGS1Jea6WPR2irly_T-JSZAmY0g?hl=en&authuser=0
Link for Observers: https://plus.google.com/events/c42doafcrpf6pta39jskgrho7t4
ping @dougwilson crandmck, is there going to be a meeting today? I don't see any issue opened about it?
Myself & Rand will be in Austin, TX for the Node.js Interactive NA. This is a meta issue to coordinate any kind of meetups around this conference :)
from jshttp/content-type#7 (comment) and from the TC meeting w/ @wesleytodd
my thoughts:
prepublish step.my questions:
<script> tag users, but not bower usersbabel? this will allow including polyfills and/orbrowserify module + tests -> running in the browser? i'm sure there are some edge cases, maybe polyfills like setImmediate() support.mime-db in the browser might be excessively largegoing forward, i'd like to build a sample repo for standardizing all modules including (most of which is already pretty standardized thanks to @dougwilson):
if we all agree on it, i don't mind making the PRs for a lot of the modules to make them all consistent
thanks for all your work @dougwilson. i haven't been really involved in express for a while, but i'd still like to help. let me know how i or anyone else can help:
etc.
i know you are particular on how you do things, so it would be great if you wrote it down :) i'll be sure not to publish myself so i don't mess it up ;)
This is an issue to discuss if we want to move the multiparty module into the Express.js TC (probably under the pillarjs organization). I know I personally use it a lot, and have had a bunch of work go in there, but want to get how people feel about this. The module is currently offered to me if I would like to move it, and I feel like, if anywhere, Express.js would be a fine home for it.
Invited:
June 1st, 2016 - 23:30 UTC
Google Hangouts:
Link for Participants: https://hangouts.google.com/hangouts/_/hoaevent/AP36tYdSYgPMVaxBzT8rvCRVUNbke-iR1E5GveNBKwr89aZ_NErSqA?hl=en&authuser=0
Link for Observers: https://plus.google.com/events/cpb1lfkg9gkp8t9c9hvmnj30ma8
Would like to raise something that I ran into today. Multer got a pull request with a translation of the readme into Chinese. I think this is great, but I don't have any good ideas for making sure that the translation is kept up to date. Maybe this is a non-issue though, would love some input from some other maintainers. Thanks ❤️
Pull request: expressjs/multer#400
The entire community is welcome to tune in and observe the meeting live at the time below. The following people are listed here as explicit invitees to get an email notification about the upcoming meeting:
Invited:
Sep 21, 2016 - 23:30 UTC
YouTube Live
Observers & Public: https://www.youtube.com/watch?v=GFwJCd_PSsY
The entire community is welcome to tune in and observe the meeting live at the time below. The following people are listed here as explicit invitees to get an email notification about the upcoming meeting:
Invited:
July 27, 2016 - 23:30 UTC
Google Hangouts: https://hangouts.google.com/hangouts/_/crftuxkaczemjnctenrp75f67ue?hl=en&authuser=0
Link for Participants: TBD
The entire community is welcome to tune in and observe the meeting live at the time below. The following people are listed here as explicit invitees to get an email notification about the upcoming meeting:
Invited:
Aug 10, 2016 - 23:30 UTC
Google Hangouts: https://hangouts.google.com/hangouts/_/crftuxkaczemjnctenrp75f67ue?hl=en&authuser=0
We need to discuss issues that were not resolved from last meeting, plus some new ones.
express repo into separate repo per expressjs/express#2923@RoyalRajdeep proposed in expressjs/expressjs.com#684 (comment)
Each Library and Framework I use, Have their own Branding, Iconic Logos, and Color theme, But Express is still not having any specific color theme, Iconic brand Logo. We are just having a simple b/w color themed website and a very simple logo type.
If Express Js community have the same thought , then I go ahead for this part to
- Suggest a new color theme for all Express Js related stuff. (Like NodeJS has Green+Grey, and they use the same Color Combination on all their stuff, Angular has Pink+White.)
- Design a new logo for express, based on our community suggestions.
This would be something that the @expressjs/express-tc would need to approve and perhaps discuss, so that's why I created this issue.
For the Website Part I will made a proposal soon.
@RoyalRajdeep please open a separate issue for any other proposal.
Hello @expressjs/express-tc!
I am currently heading up an effort to explore whether and how to implement HTTP/2 support directly in Node.js core. The question of If we should do this is still open. To help answer that question, as well as determine the best course forward should we decide to move ahead, I would love to get input from each of you with regards to what would be the best approach from the Express point of view.
Refs: nodejs/CTC#6
The entire community is welcome to tune in and observe the meeting live at the time below. The following people are listed here as explicit invitees to get an email notification about the upcoming meeting:
Invited:
Oct 19, 2016 - 23:30 UTC
YouTube Live
TBD.
Invited:
June 15th, 2016 - 23:30 UTC
Google Hangouts:
Link for Participants: https://hangouts.google.com/hangouts/_/hoaevent/AP36tYePqCMX_ZRSR2Wv6ejyNIelwomKoju-fQi4GJJLRGUGO-reew?hl=en&authuser=0
Link for Observers: https://plus.google.com/events/cj8fjj62jbudjigf4oqqrbtet20?hl=en
After reading thru the security best practices today I realised that it puts quite a lot of focus on removing the X-Powered-By header. Seeing this my first thought was that "We should remove that header from Express 5, why be insecure out of-the-box". But upon reading further I found expressjs/express#2813 (comment) by @dougwilson, and I now think that we should instead remove the recommendation.
Sending mixed signals isn't good for our users, I think that we should either remove the header altogether, or remove any recommendations to remove it. Personally I'm leaning towards removing the recommendation to remove it from the security best practices page, but I would support moving in either direction.
What do you guys think?
The entire community is welcome to tune in and observe the meeting live at the time below. The following people are listed here as explicit invitees to get an email notification about the upcoming meeting:
Invited:
Nov 16, 2016 - 23:30 UTC
YouTube Live
TBD
Hi,
I'm running node server on some IP say 192.168.xx.xx
I have a module in my application where i can change the IP address.
Now when i change the IP to say 192.168.yy.yy, then i wait for 30 sec for the change to take effect & redirect the link to 192.168.yy.yy it doesn't happen.
Can anyone say where the problem lies?
I'm just adding this since Doug hasn't done so yet....
The entire community is welcome to tune in and observe the meeting live at the time below. The following people are listed here as explicit invitees to get an email notification about the upcoming meeting:
Invited:
July 13, 2016 - 23:30 UTC
Google Hangouts: TBD
Link for Participants: TBD
Invited:
May 4th, 2016 - 23:30 UTC
Google Hangouts:
Link for Participants: https://plus.google.com/hangouts/_/hoaevent/AP36tYf6VoNWFE34DYslhezTG8_72UHVO-NH9OCsDSKgOE2GNpZ33A?hl=en&authuser=0
Link for Observers: https://plus.google.com/events/c0sncerf8uil4l9kmlluoopq7us
@expressjs Twitter handleCurrently all the TC meetings have been automatically uploaded into my own, personal YouTube account. I don't really care, but if people want to subscribe to the channel to watch new meeting, that is kind of weird. I created a separate YouTube channel a while ago, but just now finished moving all the videos: https://www.youtube.com/channel/UCYjxjAeH6TRik9Iwy5nXw7g
Invited:
April 6th, 2016 - 23:30 UTC (2016-04-06T23:30:00-0000; http://www.wolframalpha.com/input/?x=0&y=0&i=2016-04-06T23:30:00-0000+in+local+time)
Google Hangouts:
Link for Participants: TBD
Link for Observers: TBD
Google Doc: TBD
TBD
The entire community is welcome to tune in and observe the meeting live at the time below. The following people are listed here as explicit invitees to get an email notification about the upcoming meeting:
Invited:
Jan 11, 2017 - 23:30 UTC
YouTube Live
References: expressjs/express#2818, typings/typings#322, microsoft/TypeScript#7546.
Summary: For Express 5.x, support TypeScript by packaging definitions with the project. This is used by TypeScript automatically when you add typings to the package.json. As part of the effort, there needs to be a good CI step and process in place. As the author of @typings, I have plenty of background on solving the issue, but it should be as straight-forward as possible for everyone to be involved.
An initial PR demonstrating TypeScript definitions is available at pillarjs/path-to-regexp#72 and awaiting some review. Integration with CI will be an ongoing topic, the best process is having TypeScript test files which will do type checking and runtime checking. However, the linked issue above is one approach that can also work (comparing what TypeScript knows about the .js package and our hand written .d.ts file).
I'm opening this issue to give heads up and hopefully collaborate on the final solution for Express.js 5.x.
Invited:
March 23th, 2016 - 23:30 UTC (2016-03-23T23:30:00-0000; http://www.wolframalpha.com/input/?x=0&y=0&i=2016-03-23T23:30:00-0000+in+local+time)
Google Hangouts:
Link for Participants: https://plus.google.com/hangouts/_/hoaevent/AP36tYfXMbG6d5y_pLRU6u-MOx3naD1gMFT2mdQFnRwgLTEgGM-OSQ?hl=en&authuser=0
Link for Observers: https://plus.google.com/events/cq1vt2vfc7vfcfo0de4brj9sjuo
Google Doc: TBD
Invited:
May 18th, 2016 - 23:30 UTC
Google Hangouts:
Link for Participants: https://hangouts.google.com/hangouts/_/hoaevent/AP36tYft9l2IfTLaipb-EUKkjVbZ0hILIuTmQ7IZwphrDbJXwSI71g?hl=en&authuser=0
Link for Observers: https://plus.google.com/events/cglonce2k9r7ljqqd58ovqmofn4?hl=en
The entire community is welcome to tune in and observe the meeting live at the time below. The following people are listed here as explicit invitees to get an email notification about the upcoming meeting:
Invited:
Aug 24, 2016 - 23:30 UTC
Google Hangouts
Participants: https://hangouts.google.com/hangouts/_/hoaevent/AP36tYcp3RS0PQ9vuVlZYbMsIaL_yxXBzV5GKhbz1pceJO3yd2Lg_A?hl=en&authuser=0
Observers & Public: https://plus.google.com/events/c8ken3u1ugreq013do22tkl8kgk?hl=en
As per the last TC meeting (#6) and the issue reported at expressjs/expressjs.com#607, we want a logo and a favicon for Express.
Here are the initial two proposals. The font used in the logo is "Helvetica Bold".
The favicon will be derived from the logo.
Feedback welcome 😀
The entire community is welcome to tune in and observe the meeting live at the time below. The following people are listed here as explicit invitees to get an email notification about the upcoming meeting:
Invited:
Jan 25, 2017 - 23:30 UTC
YouTube Live
This is a new discussion to live by itself stemmed from the comment at #14 (comment)
The idea is to apply eslint to our repos to help guide contributors and make it less confusing on what style to use. @LinusU suggested "standard" (http://standardjs.com/) and the style, and of course, I don't think everyone will agree with all aspects of the style, but after a lot of research, I tend to agree a vote for "standard" sounds fine to me. I found the following arguments for using standard:
@LinusU please share any thoughts you have as well.
I have already converted a bunch of jshttp organization repos to this style, at least for the repos that were pretty much literally this style before, so there wasn't any real conversion anyway.
The entire community is welcome to tune in and observe the meeting live at the time below. The following people are listed here as explicit invitees to get an email notification about the upcoming meeting:
Invited:
Sep 7, 2016 - 23:30 UTC
Google Hangouts
Participants: https://hangouts.google.com/hangouts/_/hoaevent/AP36tYeHGh-oapOWXvateGP86YEvhQn97hvJGc8azZN3D3Rzlu_Y7w?hl=en&authuser=0
Observers & Public: https://plus.google.com/events/clg06cvasareslfpfsqjl5v1f74?hl=en
This question and similar comes up now and again: expressjs/multer#318
I'm not really sure what to do, maybe we could discuss this on the next TC meeting.
On the one hand
Consider what would happen if the client sent hasOwnProperty=nope or hasOwnProperty[call]=. This would break any script trying to use req.body.hasOwnProperty(_), and having client data break server code is never good.
On the other hand we get a few request from time to time and often they are using some utility library that breaks.
I think the main point would be to be consistent throughout our packages. It seems like most packages parses the body with the prototype intact.
While I can respect the cautiousness taken in the design, I believe this is one time where it's better to be consistent as a community, regardless of whether that is right or wrong. Currently, all of bodyparser's parsers spit out an
Objectobject:
The entire community is welcome to tune in and observe the meeting live at the time below. The following people are listed here as explicit invitees to get an email notification about the upcoming meeting:
Invited:
Dec 14, 2016 - 23:30 UTC
YouTube Live
TBD
Invited:
March 1st, 2016 - 6:30pm Eastern (3:30pm Pacific)
Google Hangouts:
Link for Participants: https://plus.google.com/hangouts/_/hoaevent/AP36tYezJItkc6q3Z1E9wEw3Sp8uoxus30-oBznf8_hyZRAL3d6UnQ?hl=en&authuser=0
Link for Observers: https://plus.google.com/events/c1t25h6931767e8s357iuo2jclk
Google Doc: https://docs.google.com/document/d/1KZPRK4XnKhpVqFaQ_BjJmDxFHEm8N1xaEUfQvKLtG0E/edit
(please request access for editing)
Tomorrow (Friday March 18th) I'll be looking into what steps are necessary to get the domain repo transferred. I'm not yet certain if there are any gotchas with regards to moving a repo with an associated Apex domain. I want to make sure that there are no hiccups in the site hosting before actually moving the repository.
I will use this issue to update on the progress.
/cc @expressjs/express-tc
The entire community is welcome to tune in and observe the meeting live at the time below. The following people are listed here as explicit invitees to get an email notification about the upcoming meeting:
Invited:
Oct 5, 2016 - 23:30 UTC
YouTube Live
Viewers: https://www.youtube.com/watch?v=KhIxUWh9fCU
X-Powered-By - see #39@dougwilson knows that i struggle with it. i personally want there to be less maintenance overall. a lot of @dougwilson's time is updating modules. it probably annoys me more than him :)
seems like npm either doesn't care about 0.8 anymore and/or doesn't support it: https://twitter.com/seldo/status/712386414902521861
i believe the only blocker is express@5, correct @dougwilson?
I just was made aware of a module that has been published to npm a while ago with a confusing name: https://www.npmjs.com/package/express5
It looks like a user published the first alpha of 5.0 under the package name express5, which may likely be confusing to users. I'm not sure if we need to do anything or not, which is why I'm posting here.
The weird part is that it was published earlier this year, yet the second 5.0 alpha was out mid last year, so it doesn't seem like whoever that is is even trying to keep it up-to-date.
There is apparently an express3 and express4 package as well. ¯\_(ツ)_/¯
Due to the holidays, there won't be a TC meeting today. Next meeting will be on 11 Jan 2017.
Happy holidays, all! :-D
Email from @defunctzombie :
I would like to propose moving the hbs module (https://github.com/donpark/hbs) to the expressjs organization.
This will allow the project to get more eyeballs for issues (I don't have the same amount of time to maintain it as before) and also make it easier to manage the administrative tasks of the project (webhooks, etc). Github limits what type of admin powers you can grant to projects under a user account and as such it is harder to bring on new contributors and change settings without involving the account holder.
Don (original hbs creator and current user account holder) is ok with the migration and I believe it will benefit the module going forward so that it doesn't stagnate.
How would we proceed with moving it?
cheers,
~Roman
This was brought up during this weeks weekly discussion, but contributing to the current Express.js website is difficult. Some reasons around that difficulty is because the Markdown is not actually pure Markdown and the build toolchain is hard to use.
I'd like to take some time to open a PR that'll refactor the website into a Markdown only workflow with a JavaScript-based build step. This would fix previewing contributions inside of GitHub, and all Windows users to contribute easier.
Any objections, or concerns, I should be aware of?
As suggested by @dougwilson on Express TC meeting 11-16-2016, we should add more details to the existing Collaborator Guide, focussed around code and other convention that must be followed when opening a PR.
This will help to focus PR discussions on implementations rather than on the conventions that should have been followed.
In case anyone is interested... from Node Interactive North America 2016:
Should we put these links (or embed the videos) somewhere on the website? Doug's is most relevant since it's specific to Express; Rand's is not specific to Express, though it does use expressjs.com as an example in a few places.
Was wondering if there was a TC meeting for 7/8/2016? I didn't find an issue for that date.
Also, was wondering if it would be possible to have the minutes in a doc (e.g. google doc) to have something to quickly scan over, in lieu of watching the recording--which we'd still keep.
Invited:
March 9th, 2016 - 6:30pm Eastern (3:30pm Pacific)
Google Hangouts:
Link for Participants: TBD
Link for Observers: TBD
Google Doc: TBD
we still supporting this @dougwilson? https://github.com/pillarjs/resolve-path is starting to fail on 0.8. i think we can ditch it now...
Per TC discussion in (see #32), we'd like to have some general standards for README organization, content, style, and formatting. Let's discuss here.
The entire community is welcome to tune in and observe the meeting live at the time below. The following people are listed here as explicit invitees to get an email notification about the upcoming meeting:
Invited:
June 29th, 2016 - 23:30 UTC
Google Hangouts:
Link for Participants: https://hangouts.google.com/hangouts/_/hoaevent/AP36tYcQjyd4_YGVC2CEg8sOjLN-dI3kazwL-rGAUeCxiR1IkhamNA?hl=en&authuser=0
Link for Observers: https://plus.google.com/events/ci581faosms7mup82p8h660l134?hl=en
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.