just update npx to latest version => npm update npx

Looks like we have 2 LGTMs then, but @ljharb's wasn't properly registered since it's a comment.

@erights

Why the boolean flag? A compartment should be able to detect the templatedness of its own templates. It should not be able to detect the templatedness of other templates.

The templatedness check (without compartments) is realm-agnostic (https://github.com/tc39/proposal-array-is-template-object/issues/10) i.e. another Realm templates pass it, hence the new [[TemplateObject]] instead of reusing [[TemplateMap]] for the check. I agree moving the [[TemplateMap]] to the compartments from realms makes sense, but the regular (i.e. not compartmentalized) isTemplateObjectis not checking the [[TemplateMap]], so it doesn't change much?

I wanted to preserve this semantic for code running inside a Compartment. If this is not a requirement (and the code running inside a compartment will always be more restricted), then the signature could be changed. What is the expected behavior we're looking for in the following cases (for the Array.[prototype].isTemplateObject running inside a compartment)?

1. a cross-realm template
2. same-realm template a. created outside of compartment b. created in a different compartment c. created in the same compartment

IIUC 1, 2a and 2b should fail unconditionally, and 2c should look in the compartment-relative[[TemplateMap]], and additionally consult the configurable isTemplate? Do I get it right, that compartment.isTemplate is called implicitly for 2c?

If this is the case, we would need to know that the code executes in a compartment. It's not currently spelled out, but I guess compartments will store that in a running execution context so we could branch on that?

is there a summary of why this is needed?

@Jack-Works, see https://github.com/tc39/proposal-array-is-template-object/issues/10#issuecomment-771274276 and the rest of that issue. The summary is: to be able to virtualize isTemplateObject check in a compartment.

Hello I had the same issue as you describe. I fixed it by reinstalling node_modules and running : npx react-native start --reset-cache

when the hell its gonna resolve any update regarding this?

Need to install the following packages: create-react-app Ok to proceed? (y) y

Creating a new React app in C:\Users\Hamza\Desktop\MERN\client.

Installing packages. This might take a couple of minutes. Installing react, react-dom, and react-scripts with cra-template...

added 1919 packages, and audited 1920 packages in 8m

145 packages are looking for funding run npm fund for details

96 vulnerabilities (85 moderate, 11 high)

To address all issues, run: npm audit fix

Run npm audit for details.

Initialized a git repository.

Installing template dependencies using npm...

added 32 packages, and audited 1952 packages in 35s

145 packages are looking for funding run npm fund for details

96 vulnerabilities (85 moderate, 11 high)

To address issues that do not require attention, run: npm audit fix

To address all issues (including breaking changes), run: npm audit fix --force

Run npm audit for details. Removing template package using npm...

removed 1 package, and audited 1951 packages in 10s

145 packages are looking for funding run npm fund for details

96 vulnerabilities (85 moderate, 11 high)

To address issues that do not require attention, run: npm audit fix

To address all issues (including breaking changes), run: npm audit fix --force

Run npm audit for details.

Created git commit.

Success! Created client at C:\Users\Hamza\Desktop\MERN\client Inside that directory, you can run several commands:

npm start Starts the development server.

npm run build Bundles the app into static files for production.

npm test Starts the test runner.

npm run eject Removes this tool and copies build dependencies, configuration files and scripts into the app directory. If you do this, you can’t go back!

We suggest that you begin by typing:

cd client npm start

Happy hacking!

Okay, say I have a png-sequence of 1500 images that I need to load and play back. Not really practical to add 1500 import statements to the code. This would be simple to do with images in the public folder - not in the src. And why use build ressources on copying images from src to public if they are already optimized once and for all?

I think this is a pretty common scenario thats been overlooked.

:heavy_check_mark: Deploy Preview for react-navigation-example ready!

:hammer: Explore the source changes: 32fe3f17d09452478e70df2c66517f1954ed1d20

:mag: Inspect the deploy log: https://app.netlify.com/sites/react-navigation-example/deploys/60c708045a9be50007276b75

:sunglasses: Browse the preview: https://deploy-preview-9672--react-navigation-example.netlify.app/

Hey zhigang1992! Thanks for opening your first pull request in this repo. If you haven't already, make sure to read our contribution guidelines.

• fix: move :hello to bottom along with *
• test: add case on :params

dfsf

I am facing the same issue with react-native version0.64.1

gsd

I built a wrapper component do un-virtualize the list when scrollEnabled={false} to get around this, eg:

import React from 'react';
import { FlatListProps, FlatList as NativeFlatList, View } from 'react-native';

// Custom FlatList that doesnt try to virtualize when scrollEnabled={false}
// Do this to avoid "VirtualizedLists should never be nested inside plain ScrollViews with the same orientation" error in console
export default function FlatListWrapper<ItemT>(props: FlatListProps<ItemT>) {
  if (!props.scrollEnabled) {
    return (
      <View style={props.style}>
        {!!props.ListHeaderComponent && !!props.data && props.data.length > 0 && props.ListEmptyComponent}
        {!!props.ListEmptyComponent && (!props.data || props.data.length === 0) && props.ListEmptyComponent}
        {!!props.data && props.data.map((item: any, index) => <View key={!!props.keyExtractor ? props.keyExtractor(item, index) : `${index}`}>
          {!!props.renderItem && props.renderItem({
            item, index, separators: {
              highlight: () => null,
              unhighlight: () => null,
              updateProps: (select: 'leading' | 'trailing', newProps: any) => null
            }
          })}
        </View>)}
        {!!props.ListFooterComponent && !!props.data && props.data.length > 0 && props.ListFooterComponent}
      </View>
    );
  }
  return <NativeFlatList {...props} />;
}

test

fe

d

d

hey

hey

hey

We’re not yet asking application authors to try the release.

People won't listen (like me).

For example, TikTok has upgraded to React 18 already (https://twitter.com/Brooooook_lyn/status/1402632529270632456?s=20)

Since people want to try out fresh things immediately, I think a list of what is blocking people from upgrading is helpful and can reduce other one's time-wasting.

hey

test comment

test

<!-- Please provide a clear and concise description of what the bug is. Include screenshots if needed. Please test using the latest version of the relevant React packages to make sure your issue has not already been fixed. -->

React version: 17.0.2

Steps To Reproduce

1. Render a button and a scrollable list with a height of 150px. The list should contain an array of 15 items, making sure to set the key prop of each item to unique values.
2. Observe that you can see around 8 of the original 15 list items in view.
3. On clicking the button, insert 15 more items into the beginning of the list, once again making sure to set the key prop of each item to unique values.
4. Observe that you can now see around 8 of the new list items in view.

<!-- Your bug will get fixed much faster if we can run your code and it doesn't have dependencies other than React. Issues without reproduction steps or code examples may be immediately closed as not actionable. -->

Link to code example: https://codesandbox.io/s/keen-sound-7q5yf?file=/src/App.js

<!-- Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a repository on GitHub, or provide a minimal code example that reproduces the problem. You may provide a screenshot of the application if you think it is relevant to your bug report. Here are some tips for providing a minimal example: https://stackoverflow.com/help/mcve. -->

The current behavior

If the scroll position is at the very top of a list, after inserting new items at the beginning of the list, the new items are now visible.

The expected behavior

If the scroll position is at the very top of a list, after inserting new items at the beginning of the list, the original items should remain visible.

NOTE: When the scroll position is 1 or more pixels from the top of a list, after inserting new items at the beginning of the list, the new items remain visible as expected.

Hi! Can you clarify what would be the purpose of an issue like this? We’re not yet asking application authors to try the release.

The Alpha is focused on the library maintainers, and there will be a several months period before the Beta. It’s expected things would need adjustment early on, and I’m worried making a list of popular libraries before the authors even got a chance to try the release might be a bit premature.

We are committed to working with library authors and helping find recommendations where they’re unclear, including on this issue tracker. I’m just not sure that making a public list is the right way to kick this off.

What do you think?

Hi @RSNara , any update on this PR?

Current Behavior

I am using the navigation.navigate to go to the next screen eg code (https://github.com/Hardik500/madri/blob/master/src/components/home/Body.js#L36) to go the next screen i.e. (https://github.com/Hardik500/madri/blob/master/src/screens/Category.js)

And the App works fine for the first screen but whenever I go to the next screen in a build APK, it crashes. Also it works with no issues on development mode.

Expected Behavior

It should navigate to the next screen without throwing an errors

Steps I reproduced

• Made sure that react-native-gesture-handler is at the beginning of the index file (https://github.com/Hardik500/madri/blob/master/index.js)
• Tried changing navigation.navigate to navigation.push
• Removing node_modules and doing ./gradlew clean
• Linking the packages again manually

How to reproduce

The repository can be found here, (https://github.com/Hardik500/madri). Also for the navigation structure, you can refer to this file https://github.com/Hardik500/madri/blob/master/App.js

To run it on android just use,

• npm i
• npm run android
• And connect your phone via usb
• And click on the big button at the bottom

Your Environment

App working on development:

App working on build APK: