Important: This documentation covers Yarn 1 (Classic).
For Yarn 2+ docs and migration guide, see yarnpkg.com.

Package detail

@dolittle/webpack

In Norse mythology, the Vanir are a group of gods associated with health, fertility, wisdom, and the ability to see the future.

readme

Vanir

In Norse mythology, the Vanir are a group of gods associated with health, fertility, wisdom, and the ability to see the future.

This repository is similar in the way that it is a group of packages offering a sane combination of technologies and packages put together to bring fertility and wisdom into projects.

The project serves as a combination of packages that we have found useful. In addition to this, we've put in the necessary glue when needed to make them work together.

The goal is to provide a good starting point when creating applications and Dolittle based microservices.

Not a framework

It is vital to not look at this as a framework of any sort that owns its own concepts. Look at it as a springboard for projects with what we believe are sane combinations of technologies. There are also some interesting tools within here that stand on their own.

To set expectations even further; this is not core technology at Dolittle but serves an interest for Dolittle internally while building things like our Studio. The projects in this repository are only maintained for this sole purpose in mind. In addition we do use these projects with customers and contributions are then also coming from these projects.

Documentation

You'll find all the documentation here and specifically for getting started, you'll find here.

Contributing

We welcome contributions, all we ask is that you read our code of conduct and adhere to it, and also read through the official Dolittle contribution guide as these are the things we look for during pull requests.

changelog

[12.0.2] - 2022-2-23 PR: #270

Summary

Keep mongo clients as singleton in container per tenant id. Also checks connection state before connecting in MongoDatabase.collection.

Fixed

  • New connections being made for every call to IMongoDatabase

[12.0.1] - 2022-2-22 PR: #269

Summary

Closes #267. Thanks @rune-wikstad! I couldn't figure out how to build a remote PR.

Also moved the creation of a GitHub release and updating the CHANGELOG.md file to after the packages have been published in the .github/publish.yml action.

Fixed

  • [C#] A bug in the ValidationMiddleware setting errors to the literal string "errors" instead of the list of errors.

[10.0.0] - 2022-2-22 PR: #268

Summary

Removes the toGuid() extension method on mongodb.Binary. It was failing builds and we couldn't fix it. It has been replaced with a normal function binaryToGuid(...).

Removed

  • [TS] The .toGuid() extension methods on mongodb.Binary.

[9.30.11] - 2021-8-23 PR: #264

Fixed

  • Logging for event horizon setup from config - make it possible to trace whats going on.

[9.30.10] - 2021-8-23 PR: #263

Fixed

  • Upgraded to version 17.0.1 of the Dolittle SDK
  • Upgraded to version 2.1.3 of Dolittle Entropy Projections (for compatibility with SDK)

[9.30.9] - 2021-7-8 PR: #262

Fixed

  • [.NET] Upgrade to version 9.0.0 of the Dolittle SDK

[9.30.8] - 2021-7-8 PR: #261

Fixed

  • [Node] Upgrading to version 16.0.0 of the Dolittle SDK and 2.1.2 of the Dolittle Projections.

[9.30.7] - 2021-7-2 PR: #260

Fixed

  • [Web] Fixing so that when origin of document is HTTPS we use WSS for WebSocketLink for GraphQL and WS if HTTP.

[9.30.6] - 2021-7-2 PR: #259

Fixed

  • [TS/JS] Express callback was too late. Moved it up the stack - before the Apollo GraphQL middlewares are applied. This enables adding middlewares much earlier.

[9.30.5] - 2021-6-8 PR: #258

Fixed

  • Improved the approach to how we invoke actual validators
  • Added exception handling to catch potential errors and report them more accurately if invocation fails for validators

[9.30.4] - 2021-6-7 PR: #257

Fixed

  • Lifecycle issues for GraphQL mutations/queries/subscriptions - making sure they're transient
  • Lifecycle issues for EventHandlers - they were registered as Scoped, which effectively means per WebRequest. Problem is, they're never running in the context of a WebRequest.

[9.30.3] - 2021-5-31 PR: #256

Fixed

[9.30.2] - 2021-5-28 PR: #254

Fixed

  • [C#] Hooked up the last piece of the puzzle for event-horizons.json to be parsed and set up. Forgotten to that.

[9.30.1] - 2021-5-28 PR: #253

Fixed

  • [CLI] Ignore if the features.json file does not exist and create it when adding a feature.
  • [CLI] Scoping of tenants was wrong - we want it to be scoped right now for application level

[9.30.0] - 2021-5-28 PR: #252

Added

  • [CLI] Ability to list and add tenants for an application.
  • [CLI] Ability to list microservices within an application
  • [CLI] Ability to connect event horizons between microservices - "happy path"
  • Support for event-horizons.json file automatically loaded if present and hooked up to avoid having to write code for setting up event horizon subscriptions.
  • Added support for committing public events from GraphQL endpoints
  • [C#] GraphQL subscription for watching events from public events
  • [VScode] Experimental editor for working with application.json files in a more user friendly way.

Fixed

  • [TS] GraphQL endpoint for committing events now support object type - which can be any

[9.29.5] - 2021-5-25 PR: #250

Fixed

  • Aligning package versions

[9.29.4] - 2021-5-25 PR: #248

Fixed

  • Fixing NPM package release

[9.29.2] - 2021-5-25 PR: #247

Fixed

  • Correct package information for the CLI to be able to PackAsTool

[9.29.1] - 2021-5-25 PR: #246

Fixed

  • Unaligned version numbers

[9.29.0] - 2021-5-25 PR: #243

Added

  • [C#] Feature toggling system
  • [NodeJS] Feature toggling system
  • [React] Feature toggling system to be used on top of .NET and NodeJS backends - leveraging the GraphQL types exposed
  • Adding a new Vanir CLI with full support for the Feature system
  • Introducing VSCode extension with now support for the Feature system
  • Documentation across the board for the Feature system.
  • [C#] Start of a ProxyGenerator for generating frontend proxy objects from GraphQL schema

[9.28.4] - 2021-5-20 PR: #241

Fixed

  • [C#] Fixing so that the Client instance is set before we start the client - this will then make IoC resolver callbacks relying directly or indirectly work.

[9.28.3] - 2021-5-20 PR: #240

Fixed

  • [C#] Fixes a stack overflow when registering enums as ints if any type is recursively referencing itself anywhere in the tree.

[9.28.2] - 2021-5-19 PR: #239

Fixed

  • [C#] Support type conversion to integer for enum types on the actual ObjectTypes and InputObjectTypes used by queries and mutations. This enables enums from 3rd party assemblies.

[9.28.1] - 2021-5-19 PR: #238

Fixed

  • [C#] For consistency with the Node version, we want enums to be integers by default - by default now it adds a type conversion for this.

[9.28.0] - 2021-5-18 PR: #234

Added

  • Documentation added for how Startup works
  • Includes exception details during development on GraphQL operations

Changed

  • .AddVanir() and .UseVanir() are less opionated. If one wants the same level of opinions, use .AddVanirWithCommon() and .UseVanirWithCommon().

[9.27.1] - 2021-5-18 PR: #232

Fixed

  • [C#] Removing new() constraint on ConceptAs type provider - this was an error, it shouldn't have this constraint as we support creating instances of Concept types without default constructors.

[9.27.0] - 2021-5-14 PR: #229

Added

  • [C#] Added Hot Chocolate type interceptor for adding read only properties on object types and making them readable during execution (#226)

[9.26.0] - 2021-5-14 PR: #225

Added

  • [C#] BackendArguments now have a property called ExposeEventsInGraphQLSchema that enables you to disable the exposure of events in the GraphQL schema in development mode. This setting is set to true as default.

Fixed

  • [C#] Crash when not passing in a BackendArguments instance to .AddVanir() (#223). It is now possible to not pass anything in.

[9.25.0] - 2021-5-11 PR: #220

Added

  • MongoDB serializer and provider for concepts added - all concepts will now serialize to their primitive underlying value and back to concepts when reading from MongoDB.

Fixed

  • Filtering out properties that are read only, as we have no way of instantiating these

[9.24.0] - 2021-5-11 PR: #219

Added

  • Support for using the ASP.NET Core [Authorize] attribute and its policies for authorization

[9.23.0] - 2021-5-10 PR: #216

Added

  • [C#] IExecutionContextManager interface - making it possible not lock one into the implementation. This enables more predictability for automated tests, which could potentially have side-effects with its async local implementation for holding current.

[9.22.2] - 2021-5-7 PR: #215

Added

  • [C#] Ability to run validators on instance by consuming IValidators interface in Dolittle.Vanir.Backend.Validation namespace and call either Validate() or ValidateAsync()

[9.22.1] - 2021-5-5 PR: #212

Added

  • Noddin

[9.22.0] - 2021-5-5 PR: #208

Added

  • [C#] Added a default public filter that will forward all events applied/committed as public - this behavior can be overridden by setting PublishAllPublicEvents in the BackendArguments used in AddVanir() method to false. You can then use the Dolittle configuration callback to configure your filter instead: https://dolittle.io/docs/tutorials/event-horizon/
  • [C#] All types adorned with the [Projection] attribute are automatically registered as projections. Read more here: https://dolittle.io/docs/tutorials/projections/

Changed

  • [C#] Upgraded to version 8.4.0 of the SDK

[9.21.1] - 2021-4-29 PR: #204

Fixed

  • [C#] During GraphQL calls, all validators for a type using FluentValidation is now included automatically. Not just the first it discovers.

[9.21.0] - 2021-4-28 PR: #201

Added

  • [C#] Added a callback to the BackendArguments to be able to configure the Mongo DB settings before they're frozen for the client instance

[9.20.2] - 2021-4-27 PR: #199

Fixed

  • Apollo + GraphQL dependencies moved from React to Web - which is more correct. If you don't use React, you'll then get the dependencies we really rely on.

[9.20.1] - 2021-4-25 PR: #198

Changed

  • @dolittle/projections upgraded to v2.1.0 for supporting Guid conversion to and from Mongo

[9.20.0] - 2021-4-21 PR: #191

Added

  • Support for @graphRoot decorator to be able to root resolver classes and resolver methods to build a structured schema.
  • Preliminary support for calling event mutations directly - without type details - you give it a JSON string as event content / payload

[9.19.1] - 2021-4-21 PR: #190

Fixed

  • Fixed so that Messenger doesn't publish a message that came from the 'portal' back to the 'portal' from a content frame
  • Added the missing ? search/query string key/value to the params
  • Make sure to pass the search/query string along to the ContentFrame from the portal frame

[9.19.0] - 2021-4-14 PR: #182

Added

  • eventTypes and eventHandlerTypes can now be configured during start of host
  • BrokenRule, typically used in aggregates to convey when something is not allowed - a broken rule
  • Aggregate support for IoC purposes

Changed

  • Upgraded to version 14.3.0 of the TypeScript SDK
  • Upgraded to version 2.0.0 of the Dolittle declarative projections
  • Upgraded samples to use vrsion 5.5.0 of the Dolittle Runtime

[9.18.3] - 2021-4-11 PR: #174

Added

  • Documentation for working with the frontend and specifically React and related to the MVVM model. Fixes #172, #166, #165

Changed

  • Patch level change - non breaking - callbacks for ContentFrame / CompositionRoute is now optional

Fixed

  • Making sure to cause re-render when route changes occur as a consequence of using the INavigator. Fixes #170.

[9.18.2] - 2021-4-5 PR: #163

Fixed

  • Enabling queries and mutations to live on the same route by postfixing the types used within Query and Mutation types and their children. Postifxes are "Queries" and "Mutations" for the types.

[9.18.1] - 2021-4-5 PR: #162

Fixed

  • Event mutations should only be exposed when running in development

[9.18.0] - 2021-4-5 PR: #162

Added

  • Exposing all event types based on types discovered into the GraphQL schema under mutation. Names are linked to the typename. This allowes for mutation { events { ...nameOfEventType } }

[9.17.0] - 2021-4-4 PR: #160

Added

  • Aggregate root support through dependency injection of IAggregateOf<>
  • Updated dependencies to the latest version of the Dolittle SDK (8.3.2)

[9.16.0] - 2021-4-4 PR: #159

Added

  • ITypes now exposes the assemblies used for type discovery
  • Reflection utility methods for working with attributes and interfaces
  • Dolittle Runtime support implemented with automatic discovery of EventTypes and EventHandlers - it also hooks up IEventStore propely as a dependency that can be used and is resolved in the right context.

[9.15.0] - 2021-4-4 PR: #158

Added

  • AddVanir() now returns a Services object that holds for now the ITypes for type discovery but can then be expanded on in the future.

[9.14.0] - 2021-4-3 PR: #157

Fixed

  • Removes ".Value" for concepts being set using .SetValidator typically
  • Does not add errors that are already there - avoids duplicate error messages for same proprty if one has added multiple instances of same validator

[9.13.2] - 2021-4-3 PR: #156

Fixed

  • Skip properties in validation recursion when property type is of same as parent to avoid stack overflow exception

[9.13.1] - 2021-4-3 PR: #155

Fixed

  • Avoid getting duplicate keys for the population of validation types by type

[9.13.0] - 2021-4-3 PR: #154

Added

  • GraphRoot attribute that will enable you to set the root object - can be nested, delimited by /
  • Query attribute now supports path relative to GraphRoot or root if not GraphRoot is used - can be nested, delimited by /
  • Mutation attribute now supports path relative to GraphRoot or root if not GraphRoot is used - can be nested, delimited by /
  • Support for FluentValidations AbstractValidator - automatically hooked up on any input arguments
  • AbstractValidator<> can be for any type - any input type with a property of a type with a validator will be evaluated as well

[9.10.0] - 2021-3-31 PR: #152

Added

  • Enum naming convention adds a suffix of enum to type name

[9.9.0] - 2021-3-31 PR: #151

Added

  • ConceptAs extensions to make it easier to work with ConceptAs
  • Reflection extensions to make it easier to work with type reflection
  • Automatic hookup of Type conversion for GraphQL for ConceptAs and base type mapping. This enables use of concepts in any GraphQL construct (ObjectType) and it will map to the underlying system type it is a concept as of.

[9.8.0] - 2021-3-30 PR: #150

Added

  • Convenient Collection Extensions
  • Simple type discovery for project referenced assemblies
  • Automatic hook up of any ScalarType / ScalarType<> implementations
  • Ability to configure Hot Chocolate GraphQL properties manually

[9.7.0] - 2021-3-30 PR: #149

Fixed

  • When paths are rooted as described in vanir.json - the GraphQL paths will now be single / at the beginning.

[9.6.0] - 2021-3-30 PR: #148

Summary

Making it simpler to work with Hot Chocolate type of GraphQL - heavily influenced by GraphQL AspNetCore.

Added

  • GraphController, QueryAttribute nad MutationAttribute - as found in GraphQL AspNetCore

[9.5.0] - 2021-3-20 PR: #147

Summary

Shaping up the C# setup for resources, graphql and all.

Added

  • [C#] Support for taking dependency to IMongoDatabase and it resolve to correct tenant based on resources.json config file
  • [C#] GraphQL routes adhering to the vanir.json file setup
  • [C#] ExecutionContext setup properly based on the Tenant-ID HTTP header
  • [C#] Microservice.json configuration support added - ExecutionContext leverages this

[9.4.0] - 2021-3-20 PR: #146

Summary

Shaping up the C# setup for resources, graphql and all.

Added

  • [C#] Support for taking dependency to IMongoDatabase and it resolve to correct tenant based on resources.json config file
  • [C#] GraphQL routes adhering to the vanir.json file setup
  • [C#] ExecutionContext setup properly based on the Tenant-ID HTTP header
  • [C#] Microservice.json configuration support added - ExecutionContext leverages this

[9.1.3] - 2021-3-17 PR: #143

Summary

This fixes an undesired breaking change from version 8 to 9. Collection names would by default be the type name- but we expect the same default behavior as with Mongoose, which is making it lowercase and pluralized. This particular code is now brought in from Mongoose to make sure we have the same behavior and is as expected.

Fixed

  • Collection names are now correct; lowercase + pluralized

[9.1.2] - 2021-3-15 PR: #142

Summary

Making GuidScalar more available

Fixed

  • Exporting GuidScalar from root module @dolittle/vanir-backend

[9.1.1] - 2021-3-15 PR: #140

Summary

Exporting sub modules.

Fixed

  • To avoid consumers of packages having to import dist relative paths within the package, we now export the sub-modules as part of the top-level package (e.g. data will be @dolittle/vanir-backend/data instead of @dolittle/vanir-backend/dist/data)

[9.1.0] - 2021-3-14 PR: #138

Summary

Improved developer experience and flexibility for working with resources such as mongo database and the Dolittle even store.

Added

  • Documentation on available dependencies
  • MongoDatabaseProvider for getting IMongoDatabase instances for specific tenant (Fixes #128)
  • Adds the Dolittle client as an available dependency (Fixes #127).

Fixed

  • Exports at root level of backend - exposing common types to avoid having '/dist' in imports

[9.0.9] - 2021-3-14 PR: #136

Summary

Fixing the scaffolding.

Fixed

  • Fixes #135 - casing issue in templates.

[9.0.8] - 2021-3-10 PR: #133

Summary

Makes scaffolding of new projects correct and also makes sure IEventStore instance is for the correct tenant.

Fixed

  • Fixes so we don't use webpack-cli but webpack directly for yarn:dev scripts in package.json
  • When taking IEventStore as a dependency - it is now resolved using the correct tenant-id (#125)

[9.0.7] - 2021-3-3 PR: #132

Summary

update prod configmap template to reflect new structure

Fixed

  • update prod configmap template to reflect new structure

[9.0.3] - 2021-3-2 PR: #126

Summary

Making sure we have the right context both for regular Express middlewares and GraphQL.

Fixed

  • Fixes so that the context is correct in all call paths

[9.0.2] - 2021-2-28 PR: #123

Summary

Fixes so that the correct context is returned.

Fixed

  • Fixes so that the correct context is returned - not the default one.

[9.0.1] - 2021-2-28 PR: #122

Summary

Typo when getting HTTP header for Tenant

Fixed

  • Fixing usage of correct HTTP header for tenant; Tenant-ID not Tenant-Id

[9.0.0] - 2021-2-26 PR: #118

Summary

This pull request is a major change. The biggest change is the removal of TypeGoose and Mongoose as default - instead it leverages now the native MongoDB driver and all setup is configured for this.

Added

  • Resource system for getting resource configurations per type per tenant (#111)
  • Introducing an unobtrusive way to work with MongoDB driver and still get the benefits of custom serialization with custom types.
  • Context object configured through middleware containing the tenant identifier, user id and cookies. (#112)

Changed

  • Changing from TypeGoose to native MongoDB driver for NodeJS and configured it by default
  • TenantId on Context is now the type TenantId from @dolittle/sdk.execution

Removed

  • TypeGoose and Mongoose are both moved as dependency and hence not configured by default as a consequence
  • Environment variables for configuring database and event store access

[8.0.5] - 2021-2-18 PR: #117

Summary

This PR fixes the hardcoded "Dolittle" tenant in the k8s production configuration to be configurable per template

Fixed

  • Fix the hardcoded "Dolittle" tenant in the k8s production configuration to be configurable per template

[8.0.4] - 2021-2-17 PR: #115

Summary

We've had issues with WebPack when using the dev-server and also all of a sudden broken builds due to the html-webpack-plugin not loading the ejs template file and rendering it.

Fixed

  • Upgraded to latest WebPack
  • Upgraded to latest html-webpack-plugin
  • Removing --watch option
  • Updating templates to use webpack instead of webpack-cli directly

[8.0.3] - 2021-2-16 PR: #114

Summary

Locking down remaining dependencies on specific version.

Fixed

  • Further lockdown on version for 3rd parties - must have missed some previously

[8.0.2] - 2021-2-16 PR: #113

Summary

Gaining control over 3rd party dependencies.

Fixed

  • All third party dependencies are now locked to a specific version

[8.0.1] - 2021-1-31 PR: #106

Summary

Fixing a problem with the path for GraphQL client - needs a trailing /

Fixed

  • Added trailing slash for GraphQL paths for the client bindings

[8.0.0] - 2021-01-24

Added

  • Changelog

Changed

  • Separator for environment variables have changed from single _ to double __. The separator is used for navigational purposes within the configuration object model.
  • Restructuring documentation

[7.1.7] - 2021-01-23

Fixed

  • Fixing reference to vanir.json and not config.json in the Dockerfile generated from template

[7.1.6] - 2021-01-23

Fixed

  • Dropping --env options from scripts in package.json files in template to work with WebPack 5

[7.1.5] - 2021-01-23

Fixed

  • Fixing generated Dockerfile to reflect what is in shared in the template

[7.1.4] - 2021-01-23

Added

  • Non portal Typescript sample added

Fixed

  • Adding missing context resolution for Apollo setup (User-ID, Tenant-Id, Cookie)

[7.1.3] - 2021-01-23

Added

  • C# and .NET Core support - early days - mostly investigation

Fixed

  • Fixing microservice.scss in template to correct for non-portal microservices and for portal ones
  • Fixing lint errors in template

[7.1.1 - 7.1.2] - 2021-01-16

Fixed

  • Exposing the publicPath property from configuration - this was missing

[7.1.0] - 2021-01-16

Fixed

  • Fixing eventstore property in template

[7.0.4] - 2021-01-16

Fixed

  • Lowercasing eventstore in Vanir configuration to make it possible to override with env variables. This should have bumped the major version.

[7.0.3] - 2021-01-16

Fixed

  • Making package resolving more resilient and resolve to the correct path for package.json requires/imports in packages

[7.0.2] - 2021-01-15

Fixed

  • Removing deprecated WebPack 5 options for the Terser plugin
  • Setting correct option for production builds
  • Fixing template for WebPack when generating microservices

[7.0.1] - 2021-01-15

Fixed

  • Changing to deterministic for moduleIds for optimization - hashed is deprecated in WebPack 5
  • Fixing how mjs files are resolved

[7.0.0] - 2021-01-15

Changed

  • Upgrading to WebPack 5
  • Dropping office-ui reference for SASS files and leverage @fluentui/react directly
  • Updated all package.json files in templates to use the new way of running the WebPack devserver

Added

  • Added shebang loader for those dependencies that has a #! header on top of JS files

Fixes

  • Fixing sample dependencies to Vanir packages

[6.5.1] - 2021-01-14

Fixed

  • Using cross-env for all scripts in package.json files to make developer experience work cross platform

[6.5.0] - 2021-01-14

Added

  • Adding ESM replacement for yargs dependency to make WebPacking of backends work. MJS modules are resolved in a way that breaks the build ATM.

[6.4.1] - 2021-01-12

Fixed

  • Fixing variable name to make configurable devserver port work

[6.4.0] - 2021-01-12

Added

  • Ability to specify the WebPack devserver port from environment variable (port)

[6.3.3] - 2021-01-11

Fixed

  • Making web option on Microservice an actual boolean in the generated file rather than a string

[6.3.2] - 2021-01-10

Fixed

  • Switched to reading application.json from file instead of requiring it. Require for JSON files does not work at runtime after WebPacking

[6.3.0 - 6.3.1] - 2021-01-10

Added

  • Flexibility around root, version and template paths for plop based generation

[6.2.2] - 2021-01-10

Fixed

  • Basepath working cross-platform when generating from templates

[6.2.1] - 2021-01-10

Fixed

[6.2.0] - 2021-01-10

Changed

  • More robust handling of using the plopfile by requiring it rather than loading it. Enabling us to use the tooling in other scenarios where the file is not on disk but packaged inside with WebPack.

[6.1.2] - 2021-01-09

Fixed

  • Adding create-dolittle-microservice as an actual dependency to create-dolittle-app- causing it to work in the wild :)

[6.1.1] - 2021-01-08

Fixed

  • Fixing template for microservice.json file for route segment based on whether or not it is a portal creation

[6.1.0] - 2021-01-08

Added / Fixed

  • Render portal related files when it is the portal being created during creation of microservices

[6.0.2] - 2021-01-08

Fixed

  • Fixing route segment to be correct according to rooted or non-rooted microservices

Added

  • Adding a default portal template

[6.0.1] - 2021-01-07

Fixed

  • Adding boolean to RouteInfo indicating whether or not it is an exact match.

[6.0.0] - 2021-01-07

Changed

  • Changing RouteInfo to get the matched URL and the route information

[5.0.0 - 5.1.0] - 2021-01-07

Changed

  • Changing from paramsChanged() to routeChanged() for consistency

[4.3.0] - 2021-01-05

Added

  • Exporting RouteInfo from top level module

[4.2.0] - 2021-01-05

Added

  • ViewModels can receive route info on attached() method

[4.1.0] - 2021-01-05

Added

  • ViewModels can now implement a paramsChanged() method that gets called with route params

[4.0.0] - 2021-01-05

Changed

  • References to shared components
  • Public packages are now set to private in the templates

[3.0.0] - 2021-01-05

Changed

  • Lifecycle manager for view models added
  • Added sample

[2.5.12] - 2021-01-02

Fixed

  • Exposing Web property on Microservice definition to indicate if a Microservice has a Web frontend or not

[2.5.11] - 2021-01-01

Fixed

  • Fixing GraphQL route to guarantee having only a single slash

[2.5.10] - 2021-01-01

Fixed

  • Fixing so that all templates are rendered with the current Vanir version as reference in package.json files
  • Fixed output of the route segment to be correct dependeing on whether or not it is a portal or not

[2.5.9] - 2021-01-01

Fixed

  • Hooking up TSOA out of the box

[2.5.8] - 2021-01-01

Fixed

  • Making it possible to override the Web Dev Server port

[2.5.7] - 2020-12-31

Added

  • Adding isRooted to the template for identifying wether or not a microservice is rooted in its URL strategy

[2.5.6] - 2020-12-31

Fixed

  • Making sure the microservice Id is available at the right time during generation of applications with portal

[2.5.5] - 2020-12-30

Fixed

  • Path for portal microservice.json file fixed during adding of portal from application creation

[2.5.4] - 2020-12-30

Fixed

  • Using microservice id for identifying which Microservice is the portal

[2.5.3] - 2020-12-30

Fixed

  • Passing target directory from application creation to micrsoervice creation when wanting a portal

[2.5.2] - 2020-12-30

Fixed

  • Consistently using target directory throughout the code

[2.5.1] - 2020-12-30

Changed

  • Consistently using the destination path throughout the code

[2.5.0] - 2020-12-30

Fixed

  • References internally

[2.4.0] - 2020-12-30

Added

  • Adding useDialog() hook for working more naturally with dialogs

[2.3.2] - 2020-12-30

Added

  • Ability to generate to a preferred directory for the common plop helper

[2.3.1] - 2020-12-29

Changed

  • Changing to vanir.json instead of config.json - should have caused a major release

Added

  • Preconfigured GitHub labels for semantic versioning for pull requests in our application template

[2.3.0] - 2020-12-29

Changes

  • Templates refer to microservice.json instead of version.json

Added

  • Common types project

[2.2.0] - 2020-12-29

Changes

  • Downgraded React to version 16 due to compatibility issues with other packages

Added

  • Proxy configuration in WebPack devserver configuration
  • Adding application template files

Fixed

  • LINT fixes
  • Removed copyright headers from templates
  • Adding .hbs extension to package.json files in templates

[2.1.11] - 2020-12-26

Fixed

  • Adding running of tests to CI scripts
  • Fixing TSOA module replacement - used for building backends using WebPack
  • Exporting nested modules for MVVM and routing in React package

[2.1.10] - 2020-12-25

Fixed

  • Upgrading RXJS dependency

[2.1.7 - 2.1.9] - 2020-12-25

Fixed

  • Fixing imports for deep modules that aren't exported at root
  • Fixing imports to use the root exports from the Web package

[2.1.6] - 2020-12-25

Fixed

  • Making children optional for RoutingProps

[2.1.5] - 2020-12-25

Fixed

  • Cleaning up imports and exports to be accurate - not exporting from outside packages and such

[2.1.4] - 2020-12-25

Fixed

  • Fixing content frame for setting the current document for messenger
  • Fixing wrong imports
  • Moving messenger and making things more decoupled

[2.1.3] - 2020-12-25

Fixed

  • Fixing references for import statements - to work with packaging better
  • Moving web configurations into correct location

[2.1.2] - 2020-12-25

Fixed

  • Exporting more of the MVVM constructs at root module

[2.1.1] - 2020-12-25

Fixed

  • Fixing dist folder in tsconfig.json files

[2.1.0] - 2020-12-25

Added

  • Introducing basic routing and navigation to frontends

[2.0.5] - 2020-12-25

Fixed

  • Exporting MVVM constructors from top level module

[2.0.4] - 2020-12-25

Fixed

  • Adding types and main reference for package.json files

[2.0.3] - 2020-12-25

Changed

  • Package name changed - this should have caused a major version number

[2.0.2] - 2020-12-24

Fixed

  • Making WebPack dependencies regular dependencies - bubbling them up to consumers

[2.0.1] - 2020-12-24

Fixed

  • Exposing logger and logging from top level module

[2.0.0] - 2020-12-24

Removed

  • Elements that was brought in from other sources - changes the public API surface (tenants, microservices)

[1.0.12] - 2020-12-24

Fixed

  • Adding source to packages

[1.0.11] - 2020-12-24

Fixed

  • Adding missing metadata to packages

[1.0.10] - 2020-12-24

Fixed

  • Fixing run scripts for build pipeline

[1.0.9] - 2020-12-24

Fixed

  • Correcting metadata for all packages

[1.0.8] - 2020-12-24

Fixed

  • Adding missing files in create-dolittle-app package
  • Pulled in documentation from other sources

[1.0.7] - 2020-12-24

Fixed

  • Making WebPack package public

[1.0.6] - 2020-12-24

Fixed

  • Verbosity on publishing
  • Engine strict to true

[1.0.5] - 2020-12-24

Fixed

  • Node version 14 as minimum

[1.0.4] - 2020-12-23

Fixed

  • Backend package

[1.0.1] - [1.0.3] - 2020-12-23

Fixed

  • Adding ability to publish packages

[1.0.0] - 2020-12-23 - Initial release

Added

  • Project scaffolding
  • Crude WebPack setup for frontend
  • Dependency Inversion setup with Tsyringe
  • MVVM setup for React development
  • Initial Plop templating