
Security News
npm Adopts OIDC for Trusted Publishing in CI/CD Workflows
npm now supports Trusted Publishing with OIDC, enabling secure package publishing directly from CI/CD workflows without relying on long-lived tokens.
live-server-https
Advanced tools
tls.createServer options with SSL/TSL certificate for quick https setup for live-server
tls.createServer
options with SSL/TSL certificate for quick https setup for live-server
The module is simply an options argument for tls.createServer
that includes a valid certificate.
Install it with npm
:
npm install --save live-server-https
And use it programatically:
const tls = require('tls')
const https = require('live-server-https');
const server = tls.createServer(https, (socket) => {
console.log('server connected',
socket.authorized ? 'authorized' : 'unauthorized');
socket.write('welcome!\n');
socket.setEncoding('utf8');
socket.pipe(socket);
});
server.listen(8000, () => {
console.log('server bound');
});
live-server
live-server
expects a path to the module. So if you want to use the same instance everywhere, I'd suggest installing it globally:
npm install --global live-server-https
Then pass its directory to live-server
under the --https
flag:
live-server --https=/usr/local/lib/node_modules/live-server-https
If the above doesn't work, find the proper directory by running npm -g ls live-server-https
and adding node_modules
to the result.
You can also just install it locally and pass the directory path as --https=./node_modules/live-server-https
.
Now your live-server instance works with https
!
On first load, your browser will warn you that the certificate does not come from a trusted authority. This is good, because live-server
is not a trusted certification authority. Depending on your browser, you will need to either 'unsafely proceed' or add an exception, both of which are usually under an advanced options in the prompt.
The module just exports minimal options for a tls.createServer instance. It comes with a pregenerated HTTPS certificate created with openssl. The certificate is valid until the year 3017, so be sure to sign it again before then.
This is by Robert Pirtle. It's license is MIT.
FAQs
tls.createServer options with SSL/TSL certificate for quick https setup for live-server
The npm package live-server-https receives a total of 2,411 weekly downloads. As such, live-server-https popularity was classified as popular.
We found that live-server-https demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
npm now supports Trusted Publishing with OIDC, enabling secure package publishing directly from CI/CD workflows without relying on long-lived tokens.
Research
/Security News
A RubyGems malware campaign used 60 malicious packages posing as automation tools to steal credentials from social media and marketing tool users.
Security News
The CNA Scorecard ranks CVE issuers by data completeness, revealing major gaps in patch info and software identifiers across thousands of vulnerabilities.