Files
dealplustech/node_modules/registry-url/readme.md
Kunthawat 5171a789e9 fix: Final restoration with port 80
 COMPLETED:
1. Dockerfile uses port 80 (astro preview)
2. BaseLayout imports globals.css
3. globals.css with Tailwind v4 @theme syntax
4. index.astro has Header, Footer, FixedContact
5. All image references fixed to existing files
6. Hero uses hdpe_pipe_main.jpg
7. Product cards use hdpe001.jpg
8. pt-20 on main for fixed header

 TESTED LOCALLY:
- Build: 15 pages in 1.27s
- Docker build successful
- Port 80 working
- Images load
- CSS works

Ready for Easypanel deployment.
2026-03-12 08:58:56 +07:00

51 lines
1.2 KiB
Markdown

# registry-url [![Build Status](https://travis-ci.org/sindresorhus/registry-url.svg?branch=master)](https://travis-ci.org/sindresorhus/registry-url)
> Get the set npm registry URL
It's usually `https://registry.npmjs.org/`, but [configurable](https://www.npmjs.org/doc/misc/npm-config.html#registry).
Use this if you do anything with the npm registry as users will expect it to use their configured registry.
## Install
```
$ npm install --save registry-url
```
## Usage
```ini
# .npmrc
registry = 'https://custom-registry.com/'
```
```js
const registryUrl = require('registry-url');
console.log(registryUrl());
//=> 'https://custom-registry.com/'
```
It can also retrieve the registry URL associated with an [npm scope](https://docs.npmjs.com/misc/scope).
```ini
# .npmrc
@myco:registry = 'https://custom-registry.com/'
```
```js
const registryUrl = require('registry-url');
console.log(registryUrl('@myco'));
//=> 'https://custom-registry.com/'
```
If the provided scope is not in the user's `.npmrc` file, then `registry-url` will check for the existence of `registry`, or if that's not set, fallback to the default npm registry.
## License
MIT © [Sindre Sorhus](http://sindresorhus.com)