Skip to content

tools: add proper babel setup to migration generator  #19109

@Hotell

Description

@Hotell

We use "all in" babel configuration setup for every new package generated via plop (#18968)

While the current (temporary) workflow to boot new packages is like following:

  1. create package via plop
  2. run nx workspace-generator migrate-converged-pkg --name='package-name'

We need to setup within migration generator babel configuration based on package context instead of using everything

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions