-
Notifications
You must be signed in to change notification settings - Fork 522
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
Generated npm_umd_bundle misses package scope in package_name
#1095
Comments
I am also having this issue with |
We didn't want to dig too deep into this as we only use it in devserver. So
for now, we patched the [build file generator][1] to generate the rule with
the proper package name. You can create a patch in your workspace and use
the patch attribute on the rules_nodejs repository rule to apply it without
forking.
[1]:
https://github.com/bazelbuild/rules_nodejs/blob/162e4369dfed0dc7eaf7d9b7463305d7da4d2416/internal/npm_install/generate_build_file.js#L943
Arthur <[email protected]>于2019年9月11日 周三上午1:57写道:
I am also having this issue. Did you find a workaround?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1095>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAFH2B2VUQZMYYVB6EPX5B3QI7NZVANCNFSM4ITZEM3A>
.
--
Sent from Gmail Mobile
|
Thank you! I’ll give this a shot.
…Sent from my iPhone
On Sep 11, 2019, at 07:46, Xiaoyi ***@***.***> wrote:
We didn't want to dig too deep into this as we only use it in devserver. So
for now, we patched the [build file generator][1] to generate the rule with
the proper package name. You can create a patch in your workspace and use
the patch attribute on the rules_nodejs repository rule to apply it without
forking.
[1]:
https://github.com/bazelbuild/rules_nodejs/blob/162e4369dfed0dc7eaf7d9b7463305d7da4d2416/internal/npm_install/generate_build_file.js#L943
Arthur ***@***.***>于2019年9月11日 周三上午1:57写道:
> I am also having this issue. Did you find a workaround?
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <#1095>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AAFH2B2VUQZMYYVB6EPX5B3QI7NZVANCNFSM4ITZEM3A>
> .
>
--
Sent from Gmail Mobile
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Also came across where I've not found problems with packages that aren't namespaces like afaik 0.38.3 should have the patch above unless im missing something. Example build rule:
|
🐞 bug report
Affected Rule
npm_umd_bundle
https://github.com/gregmagolan/rules_nodejs/blob/27e2b68da628f5dd1c9f109f2cf605a30f4b7baa/internal/npm_install/generate_build_file.js#L533
Is this a regression?
No
Description
For scoped packages, the
ts_devserver
willrequire()
the package using it's scoped package name (say,@scope/pkg
). However, the generatedumd
file only uses the last segment of the name (pkg
), which doesn't match the required name.🔬 Minimal Reproduction
🔥 Exception or Error
🌍 Your Environment
Operating System:
Output of
bazel version
:Rules version (SHA):
Anything else relevant?
The text was updated successfully, but these errors were encountered: