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

dev-app has 404 for localize-init bundle when deployed to firebase #22943

Closed
jelbourn opened this issue Jun 9, 2021 · 1 comment · Fixed by #22961
Closed

dev-app has 404 for localize-init bundle when deployed to firebase #22943

jelbourn opened this issue Jun 9, 2021 · 1 comment · Fixed by #22961
Assignees
Labels
area: dev-infra Issue related to internal project infrastructure in progress This issue is currently in progress P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent

Comments

@jelbourn
Copy link
Member

jelbourn commented Jun 9, 2021

When I attempt to deploy the dev-app to firebase, the application fails to load because the umd bundle localize-init.umd.js 404s:
image

I poked around tools/system-config-tmpl.js and couldn't find anything that seemed wrong for the localize package.

My most recent successful deployment was May 19th. @devversion any thoughts as to what's going on?

@jelbourn jelbourn added P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent area: dev-infra Issue related to internal project infrastructure labels Jun 9, 2021
@devversion devversion added the in progress This issue is currently in progress label Jun 10, 2021
devversion added a commit to devversion/material2 that referenced this issue Jun 11, 2021
The `@angular/localize` package does not contain any `.metadata.json`
files, or an `ANGULAR_PACKAGE` marker file. This results in the NodeJS
bazel rules not capturing the UMD files within the `NamedModule` provider.

We fix this by using the standard module provider for extracting JS
sources from TS targets and its transitive dependencies. This is more
long-term proof as the hard-coded Angular package logic within Rules
NodeJS is most likely not a long-term solution.

see:
https://github.com/bazelbuild/rules_nodejs/blob/stable/internal/npm_install/generate_build_file.ts#L1080-L1081

Fixes angular#22943.
wagnermaciel pushed a commit that referenced this issue Jun 15, 2021
The `@angular/localize` package does not contain any `.metadata.json`
files, or an `ANGULAR_PACKAGE` marker file. This results in the NodeJS
bazel rules not capturing the UMD files within the `NamedModule` provider.

We fix this by using the standard module provider for extracting JS
sources from TS targets and its transitive dependencies. This is more
long-term proof as the hard-coded Angular package logic within Rules
NodeJS is most likely not a long-term solution.

see:
https://github.com/bazelbuild/rules_nodejs/blob/stable/internal/npm_install/generate_build_file.ts#L1080-L1081

Fixes #22943.
wagnermaciel pushed a commit that referenced this issue Jun 15, 2021
The `@angular/localize` package does not contain any `.metadata.json`
files, or an `ANGULAR_PACKAGE` marker file. This results in the NodeJS
bazel rules not capturing the UMD files within the `NamedModule` provider.

We fix this by using the standard module provider for extracting JS
sources from TS targets and its transitive dependencies. This is more
long-term proof as the hard-coded Angular package logic within Rules
NodeJS is most likely not a long-term solution.

see:
https://github.com/bazelbuild/rules_nodejs/blob/stable/internal/npm_install/generate_build_file.ts#L1080-L1081

Fixes #22943.

(cherry picked from commit 9428939)
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Jul 16, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area: dev-infra Issue related to internal project infrastructure in progress This issue is currently in progress P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants