package.json

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
What really is important are the changes in the dev-ui repository and package.json in the rest (which is repeated across all other modules), npm-shrinkwrap.json and yarn.lock files are generated. T...

What really is important are the changes in the dev-ui repository and package.json in the rest (which is repeated across all other modules), npm-shrinkwrap.json and yarn.lock files are generated. The change we're introducing here is locking dev-ui dependencies, which are no longer fetched to the node_modules in the root directory, but instead, are fetched into node_modules/dev-ui/node_modules. What we're doing is moving them to the node_modules directory so they are available to the module that is relying on dev-ui, lack of them there would break the build process because of missing dependencies. For yarn.lock we're basically copying the one generated in the .tmp directory, which is where we're firing yarn up during the build process. If you have any concern, please let me know.

These changes are virtually impossible to review in-depth.

These changes are virtually impossible to review in-depth.

It is.

It is.

I've just moved it, it was already reviewed.

I've just moved it, it was already reviewed.

I don't think we need to specifically say we've increased dependent service version, please remove this.

I don't think we need to specifically say we've increased dependent service version, please remove this.

Is version correct here?

Is version correct here?

dev-ui version update has a separate review - FEOLMIS-3344.

dev-ui version update has a separate review - FEOLMIS-3344.

Not really, the release process stays the same. The only difference is that at some point we will have to update those dependencies so they don't go outdated.

Not really, the release process stays the same. The only difference is that at some point we will have to update those dependencies so they don't go outdated.

Do we need any documentation? Something needs to be changed in release process?

Do we need any documentation? Something needs to be changed in release process?

missing changelogs?

missing changelogs?

OLMIS-3696: Added dependency locking
OLMIS-3696: Added dependency locking
OLMIS-3696: Added .npmrc, npm-shrinkwrap.json, yarn.lock files and postinstall script

  1. … 3 more files in changeset.
OLMIS-1025: Updated file configurations

  1. … 5 more files in changeset.
OLMIS-1072: Changed directory paths to reflect new structure

  1. … 3 more files in changeset.
OLMIS-1072: Removed independent packages, defering to dev-ui packages

  1. … 3 more files in changeset.
OLMIS-1523: Removed blessed css

  1. … 2 more files in changeset.
Removed SC5 styleguide

OLMIS-982: Changed startup script, fixed consul registration

  1. … 4 more files in changeset.
Fixed serve task

  1. … 1 more file in changeset.
OLMIS-982: Nested locations/endpoints in service discovery.

  1. … 21 more files in changeset.
Reset karma-jasmine to older version because we use Jasmine 1.3

Updated to NodeJS 6.9.1 (LTS)

This meant:

- Grunt to v1, and related packages

- Removing SC5 Styleguide

- Adding Grunt-KSS

  1. … 2 more files in changeset.
Removing attempt to use grunt-kss

  1. … 4 more files in changeset.
Fixed grunt-kss version number

Adjusted build for grunt-kss

- Changed build ordered of bower and npm, removing double install of bower

- Changed grunt-kss verstion to 4.x

  1. … 3 more files in changeset.
Changed styleguide generator to node-kss

Removed SC5 styleguide because it was breaking with some CSS tags,

changed to node-kss which is a more basic rendering engine (with a

larger community behind it)

  1. … 2 more files in changeset.
OLMIS-1209: Added Non Full Supply Product(s) tab and add product modal

In this ticket the Non Full Supply Product(s) tab has been added. Product grid is now a state that can render either Full Supply or Non Full Supply Product(s) grids.

When Product Grid is displaying a Non Full Supply Product(s) grid, an Add button is visible that let's the user to add a product from approved products list. If the user

decides to remove the product, he can do that by clicking remove button(only items that has been added in the current session can be removed, once the requisition is saved

it will be no longer possible). Products that already are lineItems won't be available in the modal. Some refactor has been done to migrade Product Grid to its own state.

  1. … 59 more files in changeset.