open-index/open-npm huggingface dataset:
npm package: @norwegian/core-components
Description: Component library to facilitate setup of new Norwegian projects. The library contains common UI building blocks for Norwegian sites. Like buttons, accordions, grid system, filter and search boxes, and so on.
Latest version: 8.0.2

# Angular assets for Norwegian

Component library to facilitate setup of new Norwegian projects. The library contains common UI building blocks for Norwegian sites. Like buttons, accordions, grid system, filter and search boxes, and so on.

## Installation

In order to use components in your project, you have to install `@norwegian/core-components` as a dependency of you project.

```sh
npm i @norwegian/core-components
```

When it's in there, you can start importing the stuff you need. Like this:

In app.module.ts:

```typescript
import { ButtonModule } from '@norwegian/core-components';

@NgModule({
  declarations: [AppComponent],
  imports: [BrowserModule, ButtonModule],
  providers: [],
  bootstrap: [AppComponent],
})
export class AppModule {}
```

In app.component.html:

```html
<nas-button primary>Click me!</nas-button>
```



### What about the SCSS?

The SCSS files for each component is compiled and injected into the component styles. In addition to this, the variables, mixins and such is included in the distributed package and is available for your project.

If you just want the styles:   

```scss
@use '~@norwegian/core-components/styles/index';
```



### Exposing the assets

The styles refer til asset files like fonts and icons. These files are part of the distributed package and you need to expose them through the angular compiler in order for everything to come together. You do this through defining app assets in your `.angular-cli.json` file. Note that you need a license to use these assets in your site. These can be provided through NAB.

Add the following line to the `apps.assets` array:

```json
{
  "glob": "**/*",
  "input": "./node_modules/@norwegian/core-components/assets",
  "output": "./assets/"
}
```



### Tech details

- Angular 20
- AOT/JIT compatible component library
- Styles and templates are inlined at build-time, no transpiling
- Cherry-pick the modules you need. No need to include everything
- Both components and modules are exposed, making it possible to compose new modules from the components



## Adding your own component

Project is currenty not open source, and only developers which is a part of the Norwegian team can contribute with new components, features, bugfixes and patches. For the Norwegian team, please check out the internal documentation site for step-by-step introduction to the library.



## Version History

See [CHANGELOG](CHANGELOG.md) for history
npm package: @norwegian/norwegian-assets-ng
Description: Component library to facilitate setup of new Norwegian projects. The library contains common UI building blocks for Norwegian sites. Like buttons, accordions, grid system, filter and search boxes, and so on.
Latest version: 4.18.3
Deprecated: Package no longer supported. Please upgrade to @norwegian/core-components.

# Angular assets for Norwegian

Component library to facilitate setup of new Norwegian projects. The library contains common UI building blocks for Norwegian sites. Like buttons, accordions, grid system, filter and search boxes, and so on.

## Installation

In order to use components in your project, you have to install `@norwegian/norwegian-assets-ng` and `@ngxs/store` as a dependency of you project.

```sh
npm i @norwegian/norwegian-assets-ng
npm i @ngxs/store
```

When it's in there, you can start importing the stuff you need. Like this:

In app.module.ts:

```ts
import { ButtonModule } from '@norwegian/norwegian-assets-ng';

@NgModule({
  declarations: [AppComponent],
  imports: [BrowserModule, ButtonModule],
  providers: [],
  bootstrap: [AppComponent],
})
export class AppModule {}
```

In app.component.html:

```html
<nas-button primary>Click me!</nas-button>
```

### What about the SCSS?

The SCSS files for each component is compiled and injected into the component styles. In addition to this, the variables, mixins and such is included in the distributed package and is available for your project.

If you just want the styles:   

```scss
@import '~@norwegian/norwegian-assets-ng/styles/index';
```


### Exposing the assets

The styles refer til asset files like fonts and icons. These files are part of the distributed package and you need to expose them through the angular compiler in order for everything to come together. You do this through defining app assets in your `.angular-cli.json` file. Note that you need a license to use these assets in your site. These can be provided through NAB.

Add the following line to the `apps.assets` array:

```json
{
  "glob": "**/*",
  "input": "./node_modules/@norwegian/norwegian-assets-ng/assets",
  "output": "./assets/"
}
```

### Tech details

- Angular 8+
- AOT/JIT compatible component library
- Styles and templates are inlined at build-time, no transpiling
- Cherry-pick the modules you need. No need to include everything
- Both components and modules are exposed, making it possible to compose new modules from the components



## Adding your own component

Project is currenty not open source, and only developers which is a part of the Norwegian team can contribute with new components, features, bugfixes and patches. For the Norwegian team, please check out the internal documentation site for step-by-step introduction to the library.


## Version History

See [CHANGELOG](CHANGELOG.md) for history
npm package: @norwegian/search-filter
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 8.2.3.
Latest version: 2.0.4
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

# SearchFilter

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 8.2.3.

## Code scaffolding

Run `ng generate component component-name --project search-filter` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project search-filter`.
> Note: Don't forget to add `--project search-filter` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build search-filter` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build search-filter`, go to the dist folder `cd dist/search-filter` and run `npm publish`.

## Running unit tests

Run `ng test search-filter` to execute the unit tests via [Karma](https://karma-runner.github.io).

## Further help

To get more help on the Angular CLI use `ng help` or go check out the [Angular CLI README](https://github.com/angular/angular-cli/blob/master/README.md).
npm package: @norwelo/medbook-widgets
Description: Widgets for NorWelo Medbook
Author: Taner Topaç
Latest version: 0.2.2

# Medbook Widgets

This project was generated with [Angular CLI](https://github.com/angular/angular-cli) version 18.0.2.

## Development server

Run `ng serve` for a dev server. Navigate to `http://localhost:4200/`. The application will automatically reload if you change any of the source files.

## Build

Run `ng build` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publish
Run `npm login` first to login using an authorized account to login to Npm Registry before publishing.

### Considerations
First check the latest published version, and bump up the version in case it's needed.
Npm will not publish same package with an existing version.

#### Checking published versions
Run `npm view @norwelo/medbook-widgets versions` to list the current published versions.
Make sure the version to be published is not in the list of versions displayed by above command.
Update the version in package.json if necessary.
After updating the version in package.json commit the code to the repository and push/merge to main. Create a tag in github for the version, if necessary.
##### Optional
Create a release in the Github repository that complies with the version number.

### Actual Publish
Run `npm run publish`. This will run a local build, run the postbuild script to create an index.js, and a prepublishOnly script to check the current version is not already published to Npm Registry. If the current version is published the publish script will exit with error.

## Further help

To get more help on the Medbook Widgets contact with Norwelo support.