-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEAT packages] Convert to monorepo for RFC #395 #5919
Conversation
9c10dc6
to
c5a43d7
Compare
> Note: Unlike the `--global` flag in npm, `global` is a command which must > immediately follow `yarn`. Entering `yarn add global package-name` will add > the packages named `global` and `package-name` locally instead of adding > package-name globally. https://yarnpkg.com/lang/en/docs/cli/global/#toc-yarn-global --- I noticed this while working on emberjs#5919, where the following error was starting to show up in CI after converting to use yarn workspaces: ``` yarn add v1.13.0 error Running this command will add the dependency to the workspace root rather than the workspace itself, which might not be what you want - if you really meant it, make it explicit by running this command again with the -W flag (or --ignore-workspace-root-check). info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command. ```
738bb97
to
92a51ad
Compare
This adds a script to `package.json` to run our feature linting script via `yarn lint:features` rather than using `./bin/lint-features` directly. This makes it easier to run the script from the root package after converting to a monorepo like in emberjs#5919
92a51ad
to
850afc9
Compare
This adds a script to `package.json` to run our feature linting script via `yarn lint:features` rather than using `./bin/lint-features` directly. This makes it easier to run the script from the root package after converting to a monorepo like in #5919
> Note: Unlike the `--global` flag in npm, `global` is a command which must > immediately follow `yarn`. Entering `yarn add global package-name` will add > the packages named `global` and `package-name` locally instead of adding > package-name globally. https://yarnpkg.com/lang/en/docs/cli/global/#toc-yarn-global --- I noticed this while working on #5919, where the following error was starting to show up in CI after converting to use yarn workspaces: ``` yarn add v1.13.0 error Running this command will add the dependency to the workspace root rather than the workspace itself, which might not be what you want - if you really meant it, make it explicit by running this command again with the -W flag (or --ignore-workspace-root-check). info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command. ```
398a07b
to
e5848bb
Compare
e5848bb
to
0060f31
Compare
52bb4ad
to
d5ab6ec
Compare
4072791
to
b20ae3f
Compare
It seems like addons which use ED work, but apps are not building/including ED properly, at least when linked locally |
@runspired @HeroicEric when run against Ember Observer, it seems like |
is a bit of a misleading error, but it's caused by the import from |
b775139
to
a59d3e5
Compare
Co-authored-by: Chris Thoburn <[email protected]> Co-authored-by: Igor Terzic <[email protected]>
a59d3e5
to
b876a80
Compare
EmberAddons still have a babel problem, so I marked them as |
https://github.com/emberjs/rfcs/blob/master/text/0395-ember-data-packages.md
all your disk space are belong to us