Skip to content
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

chore: update bazel/create package #2665

Merged
merged 1 commit into from
May 10, 2021

Conversation

alexeagle
Copy link
Collaborator

  • put deps in a separate file
  • don't name WORKSPACE.bazel due to bug

@google-cla google-cla bot added the cla: yes label May 9, 2021
@alexeagle alexeagle force-pushed the strictDeps branch 2 times, most recently from c47d85f to da40cdc Compare May 10, 2021 04:27

${pkgMgr === 'yarn' ? yarnInstallCmd : npmInstallCmd}`;

write('WORKSPACE.bazel', workspaceContent);
write('.bazelignore', `node_modules
write('tools/BUILD.bazel', '# No targets in this Bazel package\n')
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: "No targets in this Bazel package" makes it seem to me that it's not valid to put targets in the root package, rather than saying that this package is currently empty?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

write('.bazelignore', `node_modules
write('tools/BUILD.bazel', '# No targets in this Bazel package\n')
write('tools/bazel_deps.bzl', bazelDepsContent);
// Don't name it WORKSPACE.bazel since there's a bug with managed_directories
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@alexeagle could you please share more details about this bug? Does it mean that "workspace" file should be used always without .bazel extension, or it affects only bazel/create package?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@gregmagolan is tracking down the bug which hasn't been filed upstream yet. It affects everyone, not just this bazel/create package.

- put deps in a separate file
- don't name WORKSPACE.bazel due to bug
@alexeagle alexeagle merged commit 519cf85 into bazel-contrib:stable May 10, 2021
twheys pushed a commit to twheys/rules_nodejs that referenced this pull request Jan 13, 2022
- put deps in a separate file
- don't name WORKSPACE.bazel due to bug
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants